KeePassXC 2.3 Migration Guide
2018-03-03 5 minutes
- It’s actively maintained, unfortunately unlike KeePassX
- It’s open source, and easy to contribute to, as I have
- It’s got all the features I need, like TOTP and Browser Integration
- Cross platform (not KeePassXC specific)
2.3 is the first major release since the split from KeePassX, and it brings with it a lot of new features:
- Support for the KDBX4 database format
- Support for binary key files, over the legacy XML format
- Native messaging for browser integration (to replace KeePassHTTP)
- SSH Agent integration
These new features require some changes to the system, your database file, and browser. There’s little canonical documentation on how to upgrade to use these features, so I’ve written my own!
KDBX4 is the latest version of the KeePass database format. There are many format improvements, including support for Argon2, custom data in groups and file attachments to entries. Full technical information, and the exact changes can be found on the KeePass website, however it’s not necessary to actually know how it works.
To migrate to KDBX4, you must change the Encryption Algorithm to “ChaCha20”, and the Key Derivation Function to “Argon2”. These can both be done in the Encryption settings for your database (Database > Database Settings).
If you’re planning to use your database on less-powerful hardware, such as a phone, you’ll want to set the transformation rounds low. Argon2 is far more computationally intensive compared to PBKDF2. Using the 1-second benchmark button suggests using just 23 rounds. Where before I used 20,000 rounds of PBKDF2, I now use just five rounds of Argon2, to ensure it opens in reasonable time on my phone.
New Key Files
The new key file format enables using any file as a key file for your database, rather than the XML format. This means rather than using a 45-bit key in an XML file, you can use any file of any size.
Generating a new key
The first step to change your key, is to generate a new key. Whilst KeePassXC can generate them itself, they’re not long enough for my liking (They’re perfectly secure, I just like to be overkill!).
The method suggested in the implementation PR is:
dd if=/dev/urandom of=keyfile.key bs=2048 count=1
This generates a 2048-bit key file using the system’s random number generator which is perfectly secure enough to generate random numbers, but, I like to use something even more secure:
head -c 65535 /dev/zero | openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt > keyfile.key
The above uses a mixture of OpenSSL, and the system’s random number generator. I don’t exactly know what the command is doing, but it looks more complex, so that must mean it’s more cryptographically secure, right?
Install the new key
To use the new key, you need to change the key file in the master key settings (Database > Change master key). Select the new key, and enter your current password, and apply. As this re-encrypts the database with a new master key, you can enter a new password here to change it.
Once the key is installed, I backed up the old key offline (just in case), and deleted it.
Native messaging is a way of two processes communicating in a secure-ish manor. In this case, it means the browser can communicate with KeePassXC in a way that means other applications can’t.
Before, the browser communicated with KeePassXC over HTTP, using the KeePassHTTP protocol. This had the benefit of being very easy to implement a client for, as it’s just standard web traffic. The downside is that it involved starting a web server on an internal port, meaning any process on your computer could connect to the web server and thus communicate with KeePassXC, this includes browser sessions. Although requests had to be signed, it still isn’t very good for security.
As this change is such a large one, there’s an Official migration guide, which walks through how to do it correctly.
Once your browser is completely setup and migrated, you should uninstall the extension, disable KeePassHTTP, and remove the “KeePassHTTP Settings” entry, as it’s not necessary any more.
KeePassXC now also has support for manipulating the SSH Agent, making it possible to store SSH keys inside KeePassXC. When the database is opened, keys are added to the agent and accessible to other SSH-enabled applications like
Enabling SSH Agent support
To enable SSH agent support, visit the “SSH Agent” settings pane, and tick the box. This will require restarting KeePassXC. After this, it will start communicating with the SSH agent using the socket defined at
Adding your SSH Keys
With the SSH now enabled, a new “SSH Agent” tab appears in the entry edit view.
To pair the key with this entry, you should attach it from the “Advanced” pane. You only need to attach the private key, as this often contains the related public key as part of the file. Then, from the “SSH Agent” pane, select the attachment as the primary key. This should populate the “Public key” section with the respective public key.
I’ve also set the key to be automatically added and removed from the agent, rather than manually. It’d be nice if this could be changed / defaulted globally.
Now, the keys are accessibly to use for authentication.
These new features of KeePassXC are completely optional. However, KeePassHTTP and legacy key files are considered deprecated, and may be removed in upcoming releases. So, might as well update now!