Project

General

Profile

Actions

Todo #14769

closed

Increase timeout for password entry when restoring an encrypted configuration via ECL

Added by Chris Collins 7 months ago. Updated 6 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Backup / Restore
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.09
Release Notes:
Default

Description

Reporting on behalf of a friend, he installed 2.7.0 fresh using a password protected backup, as he was typing the password, the prompt expired and it automatically proceeded. This was repeated on each attempt. He managed to proceed (with the backup restoration) only by typing in the password very fast.

Actions #1

Updated by Jim Pingle 7 months ago

  • Status changed from New to Incomplete

Exactly which method were they using to restore the encrypted config.xml?

Was it on a USB drive during the installation ? On a USB drive during the first boot ( ECL )?

I don't see any kind of a timeout that would happen during the installer-based restore when it prompts for a password.

During the ECL style restore it looks like it may have a 30 second timeout we could consider increasing: https://github.com/pfsense/pfsense/blob/master/src/etc/rc.ecl#L204

But before we do that we need confirmation of exactly what they're seeing and when.

Actions #2

Updated by Chris Collins 7 months ago

I will be back hopefully soon with confirmation.

Actions #3

Updated by Chris Collins 7 months ago

I think it is the ECL he didnt specify which link, but told me the process in more detail which sounds like the ECL to me, so I think you have found the right thing to adjust, I apologise for the original incorrect information.

Thanks

Actions #4

Updated by Jim Pingle 7 months ago

  • Tracker changed from Bug to Todo
  • Subject changed from Password protected backup - password prompt times out on install based recovery to Increase timeout for password entry when restoring an encrypted configuration via ECL
  • Status changed from Incomplete to In Progress
  • Assignee set to Jim Pingle
  • Target version set to 2.8.0
  • Plus Target Version set to 23.09
  • Affected Version deleted (2.7.x)
  • Affected Architecture deleted (amd64)

Bumping up that timeout to 60s should be safe. I'll commit that shortly.

Updating the subject and issue type to more accurately reflect the request.

Actions #5

Updated by Jim Pingle 7 months ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100
Actions #6

Updated by Jim Pingle 7 months ago

  • Status changed from Feedback to Resolved

Timeout is now 60 seconds in snapshots.

Actions #7

Updated by Jim Pingle 6 months ago

  • Target version changed from 2.8.0 to 2.7.1
Actions

Also available in: Atom PDF