Expected Behavior

Database should save and be able to reopen afterwards.

Current Behavior

Saving any existing database will cause it be impossible to open, provided a yubikey is configured with HMAC.

Possible Solution

Currently testing work around, by removing HMAC and reapplying it after update.

Update: Reapplying HMAC after the update and saving the database still corrupts the HMAC afterwards.
Full removal is required.

Update II: Opening the database and resaving it as AES-KDF (KBDX 4.0) or Argon2 instead of AES-KDF (KBDX 3.1) makes the database accessible even when saved.

Steps to Reproduce (for bugs)

1. Open 2.20 KeepassXC database
2. Save as X. Any automatic save will also work.
3. Open the saved file.
4. Should prompt HMAC error.

Context

Debug Info

KeePassXC - Version 2.3.0
Revision: 4c0ed74

Libraries:

• Qt 5.10.1
• libgcrypt 1.8.2

Operating system: Arch Linux
CPU architecture: x86_64
Kernel: linux 4.15.2-1-vfio

Enabled extensions:

• Auto-Type
• Browser Integration
• Legacy Browser Integration (KeePassHTTP)
• SSH Agent
• YubiKey