-
Notifications
You must be signed in to change notification settings - Fork 348
Description
Thank you for your KeePassDroid app — it's really helpful. There are a few issues I’d like to bring to your attention:
Loss of database access via SAF with biometric login:
After enabling biometric login and opening the database via SAF (content://...), a "File not found" error appears after device reboot or cache clearing, even though the file is still physically present. This happens because the app does not persist the URI permission using takePersistableUriPermission().
Clipboard clearing doesn't work:
The clipboard clearing function doesn’t trigger. No matter the configured delay, copied data remains in the clipboard indefinitely, which poses a security risk, especially for passwords.
Master password remains visible after biometric cancel:
If the master password is entered and biometric authentication is canceled, the password stays visible in the input field. It would be more secure if the field cleared or masked the password — similar to how KeePassDX works after a failed login attempt.
I would be very grateful if you could address these issues in future updates.