It happened again: “HMAC mismatch” when unlocking KeepassXC database with my OnlyKey as hardware key.
Update: Please see my latest post below for the probable issue (saving KeepassXC database after inactivity timeout of OnlyKey seems to alter the HMAC authentication).
New topic as I’m sure that I didn’t change ANYTHING with my OnlyKey. Two hours ago I could easily unlock my KeepassXC database, now I get the dreaded “HMAC mismatch”. All I did was adding some new passwords to my KeepassXC database, which lives in a Cryptomator container, so totally normal usage.
I’m not sure where the problem lies – with OnlyKey, or KeepassXC. I re-wrote the HMAC key to the OnlyKey, and also used my backup key (which has the same HMAC key), to no avail.
I can’t be the only one with this issue – is this problem well-known and addressed anywhere?
Again, my setup is:
- KeepassXC database stored within Cryptomator containes, which resides on Dropbox.
- KeepassXC database secured with OnlyKey as hardware key.
- Latest versions of KeepassXC and OnlyKey.
Edit: See update below – I got it to work, but only if the OnlyKey is not unlocked. Before it worked when the OnlyKey was unlocked. What gives?