You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Completely automatically, using the saved master key.
It might be useful to add a middle-ground solution between these extremes. Specifically, before unlocking the database with the saved master key, ask the user to enter a few first (or last) symbols of the master password. After one failed attempt, fallback to full master password.
Considering some may be using a strong master password I propose to prefer using a simple PIN code as a "middle step" - easier and faster to type compared to for example "a5%_" (takes more time + requires the user to switch the keyboard layout a few times)
@id-kemo, while debugging Quick Unlock in KeePassB, its developer changed his master key to "old_master_key + a few lowercase letters". Just sayin' :)
@Thunder33345, the App Lock is independent from this, it protects the app.
The Quick Unlock password is intended for unlocking the databases, once the app has already been unlocked. It is a time/security tradeoff between the existing options: more secure than automatic unlock, but faster than entering the full master password.
Currently, a database can be opened in two ways:
It might be useful to add a middle-ground solution between these extremes. Specifically, before unlocking the database with the saved master key, ask the user to enter a few first (or last) symbols of the master password. After one failed attempt, fallback to full master password.
[Thanks, u/deviltrombone]
The text was updated successfully, but these errors were encountered: