-
-
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
Direct QuickUnlock without prompting user to confirm unlocking attempt #9030
Comments
Hello @droidmonkey, release 2.7.5 is out and this feature seems not to be in it. Is that correct? Thx and cheers, |
The request is still open, we ended up not working on this one. |
* Fix #7892 - Pressing escape when the quick unlock prompt is shown will now go back to the main unlock dialog view. * Fix #9030 - Quick unlock will be automatically invoked in the unlock dialog upon being shown. * Fix #9554 - Quick unlock application setting will be updated every time the settings widget is shown instead of just on first launch.
* Fix #7892 - Pressing escape when the quick unlock prompt is shown will now go back to the main unlock dialog view. * Fix #9030 - Quick unlock will be automatically invoked in the unlock dialog upon being shown. * Fix #9554 - Quick unlock application setting will be updated every time the settings widget is shown instead of just on first launch. * Show warning that quick unlock is not enabled if user cancels Windows Hello prompt. This should limit people thinking there is a security issue. * Disable quick unlock in gui tests
* Fix #7892 - Pressing escape when the quick unlock prompt is shown will now go back to the main unlock dialog view. * Fix #9030 - Quick unlock will be automatically invoked in the unlock dialog upon being shown. * Fix #9554 - Quick unlock application setting will be updated every time the settings widget is shown instead of just on first launch. * Show warning that quick unlock is not enabled if user cancels Windows Hello prompt. This should limit people thinking there is a security issue. Also improve documentation describing this behavior. * Disable quick unlock in gui tests
* Fix #7892 - Pressing escape when the quick unlock prompt is shown will now go back to the main unlock dialog view. * Fix #9030 - Quick unlock will be automatically invoked in the unlock dialog upon being shown. * Fix #9554 - Quick unlock application setting will be updated every time the settings widget is shown instead of just on first launch. * Show warning that quick unlock is not enabled if user cancels Windows Hello prompt. This should limit people thinking there is a security issue. Also improve documentation describing this behavior. * Disable quick unlock in gui tests
* Fix #7892 - Pressing escape when the quick unlock prompt is shown will now go back to the main unlock dialog view. * Fix #9030 - Quick unlock will be automatically invoked in the unlock dialog upon being shown. * Fix #9554 - Quick unlock application setting will be updated every time the settings widget is shown instead of just on first launch. * Show warning that quick unlock is not enabled if user cancels Windows Hello prompt. This should limit people thinking there is a security issue. Also improve documentation describing this behavior. * Disable quick unlock in gui tests
AWESOME, thank you :-D |
This is only for the modal dialog at this point, not the main window. |
What exactly is the modal? |
Mostly when you unlock your DB from the browser extension. |
OK, never using this. I was referring to the main window than, as stated in my initial post. Why is my suggestion closed, when what I requested is not implemented? or will it come, too, in next release? |
We will consider implementing it in a future version, but this is closed because we have implemented what we want to right now. |
Such a pity, I was really looking forward to this. It's quite annoying to must have click on unlock few dozen times a day although it's more than obvious that one wants to use the application 😔 |
Usually, you can also just press enter. |
Hello @phoerious , yes, I am aware of that but it doesn't make a great difference, if user must click or press. |
* Fix #7892 - Pressing escape when the quick unlock prompt is shown will now go back to the main unlock dialog view. * Fix #9030 - Quick unlock will be automatically invoked in the unlock dialog upon being shown. * Fix #9554 - Quick unlock application setting will be updated every time the settings widget is shown instead of just on first launch. * Show warning that quick unlock is not enabled if user cancels Windows Hello prompt. This should limit people thinking there is a security issue. Also improve documentation describing this behavior. * Disable quick unlock in gui tests
* Fix keepassxreboot#7892 - Pressing escape when the quick unlock prompt is shown will now go back to the main unlock dialog view. * Fix keepassxreboot#9030 - Quick unlock will be automatically invoked in the unlock dialog upon being shown. * Fix keepassxreboot#9554 - Quick unlock application setting will be updated every time the settings widget is shown instead of just on first launch. * Show warning that quick unlock is not enabled if user cancels Windows Hello prompt. This should limit people thinking there is a security issue. Also improve documentation describing this behavior. * Disable quick unlock in gui tests
As discussed with @phoerious and @droidmonkey in #keepassxc:mozilla.org today, I'd like to be directly prompted for my fingerprint when QuickUnlock is enabled and the application get the focus after the first lock.
As of now, once the user has unlocked the DB for the first time and has enabled QuickUnlock, every time the app is locked and is back in focus because the user wants to use it, user first must confirm that he/she want's to actually unlock before QuickUnlock modal is shown.
As most users will activate the application for exactly that reason rather than by accident, it should be either the standard behavior or at least an option for user to select that QuickUnlock is automatically triggered. In case the application is in focus by accident, user can still abort the QuickUnlock and thus return to the main screen. Even with more than one DB open, this could be applied for the last open DB ignoring all other open DBs.
The text was updated successfully, but these errors were encountered: