adding security layers to 2.7.9 causes database corruption issues with key file and yubico 5c nfc #11253
-
I am using yubico-authenticator-7.0.0-linux app and Ubuntu 24.04.1 LTS. Forgive me, I am new to using KeePassXC. I don't see anything off-putting from the Yubico Authenticator app but the KeePassXC app seems to have display rendering issue after importing database from CSV files for a few seconds then the app is displaying normal as it should. I set the basic setting to 5.0 seconds for decryption time. I create key file + challenge response with Yubico 5c nfc. It has database corruption issue after it's created, then lock up the database, and test it by opening up the database with either yubico 5c nfc or key file both of those don't seem to work opening the database. Then I get a red message in the app saying if you try it again it could be corrupted. I can get the KeePassXC app to work only with password and no additional security layer. I tried restarting the app and recreating the database several times but cannot get it to work the way I want it to. What can I do to resolve this kind of problem? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 9 replies
-
Hello, there is a bug in 2.7.9 that sets your password to an empty string if you don't "reset" it while adding a yubikey and/or key file. Make sure you have all three protection panes with information, then press OK to save it. If you see a message about a weak password then you didn't avoid the bug. |
Beta Was this translation helpful? Give feedback.
At this point just create a new database and set the password, key file, and yubikey right at creation. You really don't need a key file if you are using yubikey, just a hint.