-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UX improvements to unlock screen #835
Comments
Thanks for your continued UX testing on KeePassXC. This time, however, we can't really change anything (not everything at least). We do not know what went into the master key and that is by design. All keys are combined into a single large master key which is used for encrypting the database and there is no way of knowing from a given database how to decrypt it. We actually don't even know of it is a valid database at all (hence the "wrong master key or database corrupt" message when you enter the wrong password). We already save in the config file recently used key files and Yubikeys and then pre-select the boxes on demand, which gives an attacker more information than they need to have, already. But they still need to have the config file, from the database alone it's not possible to get this kind of information and we won't change that. But from the config file alone, we can't hide unnecessary input fields for two reasons:
|
My only comment is it might be better to say at the top: Enter credentials to unlock [database file name] Then show the path below. This is critical information especially if you open more than one database (ie on launch |
@jsha I agree that "master key" might be a confusing term. @droidmonkey it might be a good idea to rename it to credentials so that it's more generic and less confusing for the user, as we also discussed in #813 . That being said, I think we should stick to one term only, so if we decide to use credentials instead, we should change it everywhere in the UI. Right now it's also used in the |
The heading of the macOS main window is Unlock database, instead of Enter master key. Why are they different? "Unlock database" is perfectly fine. |
Another UX detail that nags me is the "Challenge Response" checkbox, which is not always automatically checked when one clicks refresh. If I open KeePassXC, then plug in my YubiKey and tab my way to focus the "Refresh" and press space to detect the newly plugged-in security key, the checkbox is not checked automatically. But if I instead use my mouse to click the refresh button, the checkbox is automatically checked. |
Completed by #3287 |
Right now, when you try to unlock a password database, it looks like this:
I think there are some issues here:
Thanks for listening! :-)
The text was updated successfully, but these errors were encountered: