Replies: 3 comments 11 replies
-
|
You can only have 1 per database. There is no sense to have 2 or more. |
Beta Was this translation helpful? Give feedback.
9 replies
-
|
Got it, thank you! I should mention this though:
When the database has both a password and a hardware key, and you leave the
password field blank, the resulting unlock error says HMAC mismatch instead
of, say, invalid composite key.
…On Thu, Sep 22, 2022 at 3:35 PM Jonathan White ***@***.***> wrote:
That only applies after you have opened the database with a specific key.
you can open a database with any key that has the right credentials after
you lock it.
—
Reply to this email directly, view it on GitHub
<#6344 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKZJ5462SJNRZNN6GGWHD3V7S7KPANCNFSM4Z3MSSSQ>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Actually, use two YubiKeys per KeePassXC database is not that hard, just make sure your two or more YubiKeys has the same challenge response secret. I have an article Use Multiple YubiKeys for KeePassXC about this issue. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all!!
I'm testing Yubico Yubikeys 5 NFC. In general, we use KeePassXC to save sensible information. KeePassXC accepts yubikeys but just one... Anyone know if it possible to add more than one to a kdbx file?
Thanks a lot!
Beta Was this translation helpful? Give feedback.
All reactions