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

TOTP for securing your KeePassXC database #6325

Closed
QuAzI opened this issue Mar 23, 2021 · 3 comments
Closed

TOTP for securing your KeePassXC database #6325

QuAzI opened this issue Mar 23, 2021 · 3 comments

Comments

@QuAzI
Copy link

QuAzI commented Mar 23, 2021

As it is too easy to get Password+File in compromised system and YubiKey is not distributed enough and may raise questions and can't be used with phone (KeePassDroid n other forks) it would be nice to have TOTP solution.
The same way TOTP should be required only first time when you try to open container with specific path from current user and then this part of key should be encrypted with machine id as salt and stored in depth of user settings.

@droidmonkey
Copy link
Member

This is not possible. If you want a second factor you can use a YubiKey or OnlyKey or a key file that you store separately from the database.

@QuAzI
Copy link
Author

QuAzI commented Mar 23, 2021

I want THIRD factor without a highly specialized device that attracts extraneous attention. As example in some countries you can have problems even with government if they found non licensed crypto devices. Also this devices you can't buy locally

@droidmonkey
Copy link
Member

It's not possible to use TOTP in this manner. Please read on other issues requesting this feature.

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

No branches or pull requests

2 participants