This plugin for KeePass 2 password manager is intended for fast authorization with pin or biometrics to a database after its first unlock using Windows Hello technology.

With this plugin you may:

1. Unlock your database with your masterkey/keyfile/other provider;

   

2. Lock the database (for example, applying autolock on minimize);

3. When you try to unlock it again, if Windows Hello is available on your system and active for the database, a Windows Hello prompt will be shown over a classic KeePass unlock prompt;

   

4. Profit!

This plugin relies on Windows Hello API and its requirements.

There are some known issues with Windows Hello reported by community. Please, check here before write issue.

Tested on Microsoft Surface Pro 2017 with KeePass 2.39.1 and 2.42.1.

Place KeePassWinHelloPlugin.plgx into Plugins folder in your KeePass installation (by default is C:\Program Files (x86)\KeePass Password Safe 2).

Or you can use Chocolatey to install it in a more automated manner:

choco install keepass-plugin-winhello

By default this plugin holds an encrypted master password in memory and removes it upon KeePass closing. In order to be able to unlock your database via Windows Hello authentication in between KeePass launches you may check "Store keys in the Windows Credential Manager" on in the Options dialog. This will prompts you for creating a persistent key signed with your biometry via Windows Hello. The key is used to encrypt master passwords for securely storing them in the Windows Credential Manager.

The plugin integrates itself into the KeePass settings dialog.

Available settings:

• Valid time period (default: 24 hours): Choose how long a saved key will be available. Once this period has expired you need to provide your full password to unlock the database again.
• Storage location: Choose where to hold encrypted master passwords - in the KeePass process memory (by default) or in the Windows Credential Manager.
• Revoke all: Allows you to delete all stored keys.

All changes will be applied only after OK button press. You can cancel the modifications using Cancel button instead.

As you should never approve any process elevation (run as admin) if you don't trust an application (because otherwise they can do almost anything), you should never sign Windows Hello prompt if you did not request it, especially when using the persistent storage. In those cases your both passwords and PC are at risk.

Our plugin prompts you to authorize Windows Hello only in the following cases:

• You prompted to decrypt KeePass database.
• You changed the in-memory storage to the persistent one.
• If one of the operations above failed due to a known recoverable internal Windows Hello problem we could retry the prompt with an appropriate message. Warning: if an action being requested by you was actually succeeded, this one can be phishing "retry" and you should also cancel it if you're not sure.

So it works like a rule of thumb: just like you cancel an unintended UAC dialog, you should cancel an unintended Windows Hello prompt.

No sensitive information including master passwords for databases are stored by the plugin in a plain text. A database key is encrypted and decrypted using Windows Hello API in order to unlock the database.

Create junction/copy folder with KeePass.exe to root of the repository as folder named "lib". Debug "KeePassWinHello.Debug" project with "Linked KeePass" launch profile. If you add some file - don't forget to add it to KeePassWinHello.csproj, otherwise it won't be included in plgx on publish.

• Microsoft for Windows Hello technology
• JanisEst and his KeePassQuickUnlock for inspiration