r/KeePass • • Mar 27 '26 Mindblown

🚨 Warning: New FAKE website offering FAKE KeePassXC downloads!

Post image
525 Upvotes

New FAKE website offering FAKE KeePassXC downloads! Do not fall for it. The correct domain is https://

keepassxc.org without hypens!

The website is asking for your email address to access the downloads. We never ask for your email address. Do not enter your data there, it's a phishing attempt.

Fountain: https://fosstodon.org/@keepassxc/


r/KeePass • • 25d ago Heartwarming

KeePassXC 2.8.0 (Stable) released – KeePassXC

Thumbnail
keepassxc.org
188 Upvotes

r/KeePass • • Sep 10 '21

KeePassXC + KeePassDX (Android) + Sync guide. A complete starting point for new users.

182 Upvotes

Hi all.

I've recently started using KeePassXC and loved it. I got into it because of this post. So, I decided to create a tutorial series as well that covers installing and using KeePassXC (PC), KeePassDX (Android), Syncthing (For syncing Android & PC, & other PCs), as well as KeePassXC-Browser for browser integration.

I have it all in one big video here (29 mins): https://youtu.be/jL7gfM27EUA

And in a split-up series: KeePassXC, KeePassDX + Syncthing, KeePassXC-Browser, as well as a TOTP guide for KeePassXC that covers adding accounts that don't show the TOTP's key easily.

Just sharing for those who want to get into the KeePassXC project, and get some real use out of it quickly :)


r/KeePass • • Nov 27 '24

Strongbox is not open-source anymore. Do you care?

175 Upvotes

Hello everyone, KeePassium author here.

As I was writing the first lines of KeePassium back in 2018, I thought of it as a proprietary commercial project. "Commercial" was the only way for the project to live long. "Proprietary" seemed like the only way to avoid copycats. After all, what if someone takes your code and publishes your app for half the price?

That said, r/KeePass users wanted open source and the pressure was strong. So I took the leap of fate and opened the project. It remains open and protected mostly by lines in the sand instead of a proprietary brick wall. Luckily, this worked out: KeePassium gathered a community, grew into a small company, passed an audit and so we carry on.

In the meanwhile, a competing project — Strongbox — took the opposite path. It started as open source, gained popularity and then turned proprietary. (Without telling anyone, but who is perfect?)

When I mentioned that transition here on Reddit, the response was "So what, nobody cares" (My opponents deleted their comments, but their downvotes remain.) Even a certain privacy-guiding forum is deadlocked discussing whether open source matters for their passwords. So I certainly need a reality check.

Do you care if your password manager is open-source?


r/KeePass • • Oct 15 '25

KeePassDX 4.2 is out and Pssskey support is official 🎉

Post image
135 Upvotes

Available on GitHub:

https://github.com/Kunzisoft/KeePassDX/releases/tag/4.2.0

(and later on the Google Play Store and F-Droid)


r/KeePass • • Mar 14 '26

let's talk about google effectively shutting down F-droid in Auguest 2026, and its impact on trust for open source android apps

84 Upvotes

We have a lot of great free open source android options supported by small development teams (often one man). These include KeepassDX, Keepass2Android, Aegis, and perhaps ente auth (where the client is open source, and the development team is a little larger)

When it comes to trusting my security secrets (passwords, 2fa), I feel comfortable trusting these developers based on two considerations:

  1. Their source code is published publicly (FOSS)

  2. Their apk is available through F-droid, which compiles from source using a reproducible build process.

According to F-droid, this option is going away in August 2026:

If the app is not available through F-droid, we'll presumably have to get it through Google Play, where the developer himself compiles it and provides the apk to Google Play for us to download. That requires a higher degree of trust in the developer. And while I am impressed and grateful by the efforts of these developers and have ZERO reason to distrust any of them, I really don't want to have to be in a position to trust any small development team with my security secrets without some degree of transparency/oversight in both source code and compilation.

One consideration is splitting our secrets in various ways so that any individual app does not see too much of it.. That includes storing passwords in a separate app from 2fa, and using pepper with passwords. For critical passwords, I already do that, but I like multiple layers of security.

What are your thoughts? Will you make any changes if/when these changes occur?


r/KeePass • • Jan 04 '22

TIL: You can rename custom icons. All these years...

Post image
82 Upvotes

r/KeePass • • Jul 23 '21

KeePassXC and YubiKeys – Setting up the challenge-response mode

80 Upvotes

Summary

A YubiKey additionally protects the KeePassXC database, depending on your threat model and use cases.However, if you lose or damage your YubiKey you might lose access to your database. So in this tutorial I will not only show you how to add a Yubikey to a KeePassXC dstabass but also how to set up a second YubiKey as a backup and/or store the secret to program a backup/new YubiKey at a later stage with the same secret. This method is also compatible with iOS and Android clients allowing you to access your passwords on a wide range of devices.

Contents

  • · Requirements

  • · Configuring the YubiKey(s)

    • · Configure your primary YubiKey

    • · Configure additional YubiKeys (optional)

    • · Backup your stored secret (recommended)

  • · Reconfiguring your KeePassXC database

  • · Testing your new setup

  • · Compatibility with KeePassium/Strongbox (iOS) & KeePass2Android (Android)

  • · External links

Note: this tutorial is based on the excellent guides provided by the InfoSec Handbook website. I simply changed/added some content. The original article also seems offline at the time of writing this (July 2021 due to website maintenance))

Requirements

The following steps are required before proceeding:

    1. Create and save your first KeePassXC database. In the following, we assume that you already have a KeePassXC database.

  • 2. For this tutorial, we use KeePassXC 2.6.6, released in July 2021. If you install another version of KeePassXC, the setup and usage might differ. (Edit: also tested with KeepassXC 2.7.1

  • 3. Get at least one YubiKey 5 (or a similar security token). You can get two YubiKeys (one primary, one backup) as a precaution. You need a free configuration slot per YubiKey for this tutorial.

  • 4. Install the “YubiKey Manager” (ykman) to configure the YubiKeys. For this tutorial, we use the YubiKey Manager 1.2.4, released in March 2021. If you install another version of the YubiKey Manager, the setup and usage might differ. (Edit: also tested with newest version April 2022)

Note

While the original KeePass and KeePassXC use the same database format, they implement the challenge-response mode differently. If you set up the mode in KeePassXC, you can't open the database in KeePass anymore (and vice versa).

Configuring the YubiKey(s)

We use the YubiKey Manager to configure the YubiKey(s).

Configure your primary YubiKey

In the following, we assume that the second configuration slot of your YubiKey is unconfigured and free.

    1. Plug in the primary YubiKey.

  • 2. Enter ykman info in a command line to check its status.

  • 3. Enter ykman otp info to check both configuration slots. By default, “Slot 1” is already “programmed.”

  • 4. Set up slot 2 for the challenge-response mode: ykman otp chalresp -t -g 2. The parameters are “require touching the physical button to generate the response” (-t) (optional) and “generate a random secret” (-g).

You should see output similar to the following:

Using a randomly generated key: abcd…6789
Program a challenge-response credential in slot 2? [y/N]:

Press y to set up slot 2. Done

Since we want (optionally) to store the same secret in another YubiKey or make a backup of it (recommended) do not close ykman at this point.

Configure additional YubiKeys (optional)

For any additional YubiKey, you need to configure the same secret (the “randomly generated key”):

  • 1.Plug in another YubiKey.

  • 2. Enter ykman info to check its status.

  • 3. Enter ykman otp info to check both configuration slots. By default, “Slot 1” is already “programmed.”

  • 4. Set up slot 2 for the challenge-response mode: ykman otp chalresp -t 2 [secret]. This time, you need to enter the secret key (“abcd…6789”) instead of using the parameter “-g.”

You should see output similar to the following:

Program a challenge-response credential in slot 2? [y/N]:

Press y to set up slot 2. Done.

Repeat this for every other YubiKey you want to use as a backup.

Backup your secret (strongly recommended)

If you do not have a second YubiKey and/or want to program a new/backup YubiKey at a later stage you can also backup your secret key.This can be done by saving or writing down your secret key (“abcd…6789”) and storing it somewhere safe. Simply repeat the “Configure additional YubiKeys” steps with the secret key from your backup and you can use another YubiKey with the same KeePassXC database.

Reminder: if you do not have a second Yubikey configured with the same secret and do not backup your secret key you will lose access to your database if your Yubikey breaks or get lost!

Reconfiguring your KeePassXC database

After setting up the YubiKey(s), we need to reconfigure the KeePassXC database to use the YubiKey challenge-response mode.

Warning

It is unlikely that something bad happens. However, we recommend to back up your unmodified database before proceeding and not to delete it until you have tested your newly configured YubiKey(s) and backed up secret.

Reconfiguring your KeePassXC database is straightforward:

    1. Plug in any of the prepared YubiKey.

  • 2. Unlock your KeePassXC database by entering the corresponding password.

  • 3. Go to “Database” → “Database Security”

  • 4. Click “Add additional protection…” .

  • Besides the password, you can add a key file or YubiKey to protect your database further.

  • 5. Click “Add YubiKey Challenge-Response.” KeePassXC should automatically detect your YubiKey, showing “YubiKey \[serialnumber\] Challenge-Response - Slot 2 - Active Button.” If KeePassXC doesn’t detect your YubiKey, click “Refresh”

  • 6. Click “Okay.”

  • 7. Save your KeePassXC database. Done.

Since you configured the same secret on each YubiKey, you only need to do this step once.

Testing your new setup

Finally, test your new setup:

    1. Lock your KeePassXC database (e.g, press CTRL + W).

  • 2. Select your database to unlock it.

  • 3. Enter your password and select the YubiKey. You might need to click “Refresh.”

  • 4. Click “OK.”

  • 5. KeePassXC asks you to press the physical button of your YubiKey. Press it.

  • 6. Use your unlocked database.

If you have two YubiKeys, don’t forget to test both. You can also test the backed up secret by restoring it to your YubiKey and unlocking the database.

Compatibility with KeePassium/Strongbox (iOS/Mac) and KeePass2Android (Android)

The good thing about the method above is that it is compatible with KeePassium and Strongbox on iOS and KeePass2Android on Android devices. Meaning that with a YubiKey that supports USB-C (Android) or Lightning port (iOS) or NFC (iOS & Android) you can unlock you database on these devices as well. By storing the database in a remote location accessible to all your devices (example: cloud storage like Dropbox) you can work with the same database (preventing the need to manually synchronize them) on all your devices.

External links

KeePassXC
YubiKey Manager
YubiKey 5
KeePassium
KeePass2Android
InfoSec Handbook


r/KeePass • • Dec 24 '17

Thanks Keepass and anyone that works on it.

80 Upvotes

I used Lastpass for a few years before I got sick of it's interface, price, and the fact that I relied on another company for my passwords. During the summer I started the process of switching everything to Keepass. I only ever got it working with Linux and Firefox before school started and I got too busy to do the rest.

With the holiday break, I now have dropbox holding the database in the cloud, syncing to my server at home, laptop, and android phone. Key file is on my laptop and phone, backed up in my server and a spare flash drive. KeePass works incredibly well on Linux, integrating very nicely with Firefox via KeeFox; the Quantum update made it even better. On my phone I use Keepass2Android and I'm very impressed. It works incredibly well, probably better than LastPass! Dropbox syncing is almost instantaneous as well. Everything just works together much better than I ever expected and I'm very happy, especially since I'm not relying on a company anymore.. well dropbox, but I can live with that.


r/KeePass • • Mar 01 '26

Free, open-source KeePass client for iOS with FaceID support -- no subscriptions, no paywalls

77 Upvotes

Hey everyone,

I'm a security engineer and longtime KeePassXC user. I got tired of the iOS situation — Strongbox wants $50/year, KeePassium gates premium features behind a paywall, and most other options feel abandoned. So I built my own.

KeeForge is a native iOS KeePass client. Fully free, open source (GPLv3), no catches.

What it does:

  • Opens KDBX 4.x files (Argon2 + ChaCha20/AES)

  • Face ID to unlock your database

  • Face ID required to reveal or copy passwords

  • TOTP generation and copy

  • AutoFill extension — works in Safari and any app

  • Website favicons (opt-in, off by default for privacy)

  • Auto-lock with configurable timeout

  • Multiple URLs per entry (KP2A_URL fields)

  • Search across all entries

What it doesn't do (yet):

  • No editing — read-only for now, v2 will add create/edit

  • No sync — you manage the .kdbx file yourself (iCloud Drive, Nextcloud, whatever)

  • No attachments

GitHub: https://github.com/crazytan/KeeForge

App Store: https://apps.apple.com/us/app/keeforge/id6759309295

Would love feedback from this community — you're the target audience. What's missing? What would make you switch?


r/KeePass • • Jul 07 '20

KeePassXC 2.6.0 released

Thumbnail
keepassxc.org
77 Upvotes

r/KeePass • • Mar 22 '25

Confession: I thought it was KeepAss

73 Upvotes

Like before I knew it was 'KeePass' like key pass, I thought the idea was 'Keep Ass' --> 'Keep my ass protected'. I still prefer that version. Thanks for coming


r/KeePass • • Jun 06 '26

I built a KeePass plugin that makes it a native Windows 11 passkey provider (no browser extension)

69 Upvotes

I wanted to use passkeys but didn't want them locked inside Windows Hello, a phone, or a separate password manager. So I built a plugin that registers KeePass as a passkey provider in Windows 11 itself.

KeePassXC already does passkeys, but I still prefer KeePass 2, mainly because of its plugin system. It keeps the base install small and reduced to the minimum, and you only add the advanced features you actually need as plugins. Passkey support is a perfect example: if you want it, you install this plugin, and if you don't, your KeePass stays lean. So I built passkey support the KeePass way, as an optional plugin.

Once it's installed, any website or app that supports passkeys can create and use them through KeePass directly. There's no browser extension needed. When a site asks for a passkey, Windows shows KeePassPasskey in the native picker alongside Windows Hello and your phone.

A few things that mattered to me while building it:

  • Portable storage. Passkeys are saved as normal entries in your database using KeePassXC's KPEX_PASSKEY_* field format. Credentials made here can be read by KeePassXC and vice versa, so you're not locked into my plugin. I also tested them with KeePassDX on Android and they work there too.

  • Keys stay in KeePass. All key generation and signing happens inside the KeePass process. Private keys never leave it.

  • Standard algorithms. ES256, EdDSA, and RS256 are supported.

How it works under the hood: Windows 11 routes passkey operations to a COM server registered as a plugin authenticator. This project is that COM server plus a KeePass plugin that does the actual crypto, talking to each other over a local named pipe. The cryptography is handled by BouncyCastle, a well known and widely audited crypto library, so the passkey algorithms aren't hand-rolled and don't introduce their own security issues. It's also the main reason the plugin DLL is fairly large.

Requirements are KeePass 2.54+ and Windows 11 24H2 with a TPM* enabled.

Website: https://keepasspasskey.github.io

Windows Store: https://apps.microsoft.com/detail/9nwnfhjpspgz

Source (GPLv3): https://github.com/yusei36/KeePassPasskey


r/KeePass • • Sep 04 '25

Confused about KeePass, KeePassXC, and all those Android apps – what’s the difference?

67 Upvotes

TL;DR:
I’ve been using the original KeePass on Windows since 2007. Now I want it on my phone, but there are tons of Android apps (KeePass2Android, KeePassDX, etc.) and I don’t know which one makes sense. Also confused about why so many people prefer KeePassXC over the original – is it about security, features, or just looks?

Hey folks, I’m a bit overwhelmed. I’ve been using the original KeePass by Dominik since around 2007 and never really thought about having it on my phone. Recently, I figured it might be smart to also use it on mobile – and that’s where the adventure began.

There are countless Android apps calling themselves “KeePass.” Which ones do what, and why do they all exist? For example, the official KeePass website recommends these:

  • KeePassDroid (for Android)

  • KeePass2Android (for Android)

  • KeePassDX (for Android)

  • KeepShare (for Android)

  • JKeePass (for Android)

  • OneKeePass (for Android / iPhone / iPad)

Then I noticed that many of you are using KeePassXC, but I don’t fully understand why. Does the “original” KeePass have issues or security flaws that KeePassXC fixes? Or why the hype?
(BTW: is this the official KeePassXC site? https://keepassxc.org)

Sorry if this seems obvious to some, but I honestly can’t keep track of it all anymore and would really appreciate some clarification.

If necessary, I’m willing to switch to KeePassXC. But if it’s just about having a more modern design, I don’t really need it – I’m a purist on Windows, and the original setup has always been fine for me.


r/KeePass • • Sep 24 '26

KeePassXC 2.8.0-beta1 migration from Qt5 to Qt6, Auto-Type on Wayland (Linux)

Thumbnail
keepassxc.org
63 Upvotes

r/KeePass • • Aug 20 '26

Can i securely store important keys like Microsoft Recovery Key (e.g. for BitLocker) in the note section?

Post image
63 Upvotes

Is that secure or do i need to put it into the password field? I have very long Keys with extra information i am not sure if the password field will be optimal for that. Notes field seems more fitting imo, but idk... what do say the experts? If someone were to get my key he would be able to bypass my disc encryption.


r/KeePass • • Jun 04 '23

Don't Let Reddit Kill 3rd Party Apps!

Thumbnail self.save3rdpartyapps
63 Upvotes

r/KeePass • • Sep 10 '25

KeePassDX Passkeys support (Pre-Release)

Post image
62 Upvotes

KeePassDX is testing passkeys support on Android. 👍🏻

So now we can keep all of our passkeys off-line.


r/KeePass • • May 14 '25

KeePass trojanised in advanced malware campaign (check where you download from that its real)

Thumbnail
labs.withsecure.com
60 Upvotes

r/KeePass • • Sep 10 '21

KeePass 2.49 released

Thumbnail
keepass.info
59 Upvotes

r/KeePass • • Sep 10 '20

KeePass 2.46 released

Thumbnail
keepass.info
57 Upvotes

r/KeePass • • 11d ago

KeePass 2.62 Released

56 Upvotes

Hot on the heels of the 1.44 update.

https://keepass.info/news/n261104_2.62.html


r/KeePass • • Feb 19 '26

Online Password managers less secure than promised

Thumbnail
ethz.ch
56 Upvotes

r/KeePass • • Jan 10 '22

[PSA] KeePass 2.50 released!

Thumbnail
keepass.info
54 Upvotes