KeePassXC Blog

Today we are releasing the second maintenance update for the 2.5 baseline, KeePassXC 2.5.2.

This update comes with additional fixes to reported issues after our initial release. Thank you for your patience and detailed reports that allowed us to fix these problems. Overall this release brings significant stability and usability improvements to KeePassXC. Most notably are fixes to crashes when the database is stored in a cloud storage service and resolving site sub-domain matching for the browser extension.

Read more…

Today we are releasing the first maintenance update for the 2.5 baseline, KeePassXC 2.5.1.

This update comes with fixes to reported issues after our initial release. Thank you for your patience and detailed reports that allowed us to fix these problems. Overall this release brings significant stability and usability improvements to KeePassXC. Most notably the file hash checking has been reduced to every 30 seconds to eliminate lag with large databases.

Read more…

A bit more than half a year has passed since the last major release of KeePassXC, so today we are very proud to announce KeePassXC 2.5.0.

The new release comes with a large number of new features and improvements. A few key additions that are worth highlighting are the ability to create a paper backup of your database for safe storage of your credentials away from your computer, a brand-new database statistics panel, a redesigned unlock dialog, a reworked entry panel, a function to download favicons for all your entries at once, and username autocompletion based on known usernames from other entries.

Read more…

We are happy to announce KeePassXC 2.4.3, the third maintenance release of the 2.4 series!

This release fixes a couple of deployment bugs that we experienced with 2.4.2.

Read more…

We are happy to announce KeePassXC 2.4.2, the second maintenance release of the 2.4 series!

This release fixes several bugs and introduces a memory wiping feature that will reduce the risk of secrets remaining in memory after a database is locked or being swapped to disk. Combined with the existing restrictions on memory access by non-administrators, this feature increases the security of KeePassXC.

Read more…

We are happy to announce KeePassXC 2.4.1, the first maintenance release of the 2.4 series!

The new release fixes several bugs introduced in the previous feature release, including a case of possible data loss when unsafe saves were disabled on macOS and an issue with reading legacy keyfiles preventing the user from opening their database.

Read more…

After two beta releases, today we are proud to release KeePassXC 2.4.0!

With this release, we have streamlined our code, improved the user interface, and added several new and exciting features. We have merged a total of 116 pull requests that implemented 12 new features, resolved 28 bugs, and closed 73 issues.

Among the highlights of this release are a new database creation wizard, advanced search, KeeShare database sharing and synchronization, update checks, OpenSSH for Windows support, and a QR Code generator for TOTP.

Thanks to our active community, KeePassXC is now available in 40 languages! Help us translate on Transifex.

Read more…

Some of you may have seen the recent vulnerability report from ISE that details various memory attacks against 1Password and KeePass, among others. Although KeePassXC was not mentioned, we have thoroughly reviewed the report and address some questions it raises below.

Read more…

Today we announce another 2.3 maintenance release with KeePassXC 2.3.4.

This release fixes a crash while downloading website favicons and brings some minor improvements to the entry view, database merging, SSH agent functionality, and browser integration.

With KeePassXC 2.3.4, we have also updated our PPA to ship a package for the upcoming Ubuntu 18.10 Cosmic Cuttlefish, whereas 17.10 Artful Aardvark has been discontinued.

Read more…

Today we announce the third 2.3 maintenance release KeePassXC 2.3.3.

This release fixes a crash that was introduced in KeePassXC 2.3.2. The crash occurred when browser integration via proxy was enabled and prevented the application from starting if the setting was enabled in a previous version.

Read more…