Skip to content
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

How master password is stored in memory? #83

Closed
4-FLOSS-Free-Libre-Open-Source-Software opened this issue Nov 30, 2021 · 2 comments · May be fixed by #104
Closed

How master password is stored in memory? #83

4-FLOSS-Free-Libre-Open-Source-Software opened this issue Nov 30, 2021 · 2 comments · May be fixed by #104

Comments

@4-FLOSS-Free-Libre-Open-Source-Software

Missing detailed Description of how and when the master password is stored in memory.

  1. Is the master password still stored in memory for usage of only QuickUnlock Feature while check "Store keys in the Windows Credential Manager" or no? Does it prevent it from storing in memory that can be accessed from outside Keepass?

  2. How is the master password encrypted in memory ?

Additional context

https://github.com/sirAndros/KeePassWinHello#key-storage

Key storage
-----------
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.

@sirAndros
Copy link
Owner

Hi, @4-FLOSS-Free-Libre-Open-Source-Software!

Please check #104 and confirm if everything is clear now.
Thank you!

@4-FLOSS-Free-Libre-Open-Source-Software

Thanks for the clarification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants