forked from keepassx/keepassx
-
Notifications
You must be signed in to change notification settings - Fork 4
Lock database doesn't work reliably #1
Copy link
Copy link
Closed
Description
As mentioned by @fabian-z
I noticed that database locking does not work as expected - it only checks the password (and/or keyfile) but not the yubi key (I can even remove it unnoticed by keepassx).
Also, DatabaseOpenWidget does not enable Challenge Response asynchronously for me; the yubikey has to be plugged in when starting keepassx.
Steps to reproduce:
- Create kdbx with password + yk
- Add entry / test data and save
- Lock database
- Remove yk
- Unlock database with just password
Possibly other bugs.
Expected behavior:
- Removal of YubiKey after database locking should make it impossible to unlock the database.
- Async detection of re-insertion of YubiKey won't be supported.
- User will have to re-open the file manually. This may be re-explored in the future, but adds to much complexity now.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels