-
Notifications
You must be signed in to change notification settings - Fork 17
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
WinHelloUnlock stops working when update is available #25
Comments
Yes, I am aware of the issue, it was introduced when closing #12. |
It would be very helpful if you could test this |
Just tested. Still shows KeePass warning prompt at pressing Esc "Error decrypting the data. The request was cancelled by the user". Pressing OK in that prompt shows "Enter Password" prompt. It sounds like you submit the request to decrypt data BEFORE finger scan is done and processed, instead of AFTER that. Esc works well with KeePassWinHello plugin. Mark KeePass - Options - Advanced - Check for updates at KeePass startup. Then downgrade your plugin version, and re-launch KeePass. |
That is actually expected behaviour! Esc key should be equivalent to clicking cancel button!
I did that but for some reason it doesn't work. Anyway, I am asking about the issue in this thread. Is WinHelloUnlock working when it checks for updates? |
For me it doesn't, and for some reason you close bugs without testing. I don't mind though, its your plugin. What happens now:
The rest is up to you. I'm just trying to help by reporting errors to make it more convenient to use. If its enough for you to say "its expected" - this is your plugin. But some folks would move back to competitor. You also need to allow at least 48h for users to respond to your questions before closing any bug. :) |
Thanks for reporting! I closed because I could get Keepass to check for updates and the database was successfully opened, and don't worry, we can just reopen if needed. Are you using latest v1.3 release? Also, let me understand correctly, do you push Esc key on the keyboard expecting to Unlock the database? |
Sorry, I was using previous build. With latest build, there is no update anymore unless you post a new test build. So I can't test the update behavior. When Esc is pushed, I expect hidden behind KeePass Enter Password form to appear, not KeePass Error popup, it must proceed quietly with errors suppressed. |
To test this issue, downgrade a different plugin and test with latest WinHelloUnlock. |
Hope you can finish the fix without further help. :) |
Ooops, your competitor just got a new version, and it doesn't show KeePass window until finger is scanned, which is more logical, and shouldn't lead to problems like this bug. KeePass shown Update prompt again. WinHelloUnlock finger scan worked, but after closing KeePass Update prompt, the DB remained locked. So your fix didn't work. If KeePassWinHello plugin devs borrowed your method and code of storing password, they should reference you in the new release as per Github best practices. |
I don't have a competitor, I wrote this plugin for me based on KeePassWinHello to fit my needs for permanent key storage and I decided to share it for free. You are asking for a removal of a warning I feel it should stay, informing the user that the credential retrieval was canceled by himself, you just need to push Enter, Esc or click the button to get the regular Key Prompt. Remember, according to the license, this software is offered as is and you are free to use whichever plugin fit your needs better. You can also just fork the repository and make the changes you want, as I did myself with this plugin. |
As for this issue, you are right, it is not fixed! thanks for pointing that out. |
Describe the bug
When KeePass shows a plugin & package Update Prompt at launch, and user closes it, WinHelloUnlock doesn't show Scan Prompt after that and fails to work
To Reproduce
Steps to reproduce the behavior:
Expected behavior
WinHelloUnlock should show Scan Prompt and allow user to scan fingerprint and enter KeePass once KeePass Update Prompt is closed by the user.
The text was updated successfully, but these errors were encountered: