Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems. Learn more →
Keepassxc Alternatives
Similar projects and alternatives to keepassxc
-
-
InfluxDB
InfluxDB high-performance time series database. Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.
-
-
-
LibreOffice
Read-only LibreOffice core repo - no pull request (use gerrit instead https://gerrit.libreoffice.org/) - don't download zip, use https://dev-www.libreoffice.org/bundles/ instead (by LibreOffice)
-
-
-
Cryptomator
Cryptomator for Windows, macOS, and Linux: Secure client-side encryption for your cloud storage, ensuring privacy and control over your data.
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
-
-
-
-
-
bitwarden_rs
Discontinued Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs [Moved to: https://github.com/dani-garcia/vaultwarden]
-
KeePassDX
Lightweight vault and password manager for Android, KeePassDX allows editing encrypted data in a single file in KeePass format and fill in the forms in a secure way.
-
ios-application
A native, lightweight and secure one-time-password (OTP) client built for iOS; Raivo OTP!
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
keepassxc discussion
keepassxc reviews and mentions
- EU issues US-bound staff with burner phones over spying fears
- Avoid US or Take Burner Devices, Canadian Executives Tell Staff
- Your Phone, Your Data: How to Safeguard Your Digital Life When Entering the U.S.
-
2FA or Not 2FA
And one of the developers of passkeys threatened to use the specified attestation anti-feature to blackball Keepassxc's implementation when they made something not locked in enough.
https://github.com/keepassxreboot/keepassxc/issues/10407
There have been some discussions to create an export standard since then but I remain skeptical. Why was this not part of the original spec but the ban hammer was? Depending upon how this standard is implemented I can easily see it preventing export to anything but Google, Microsoft and Apple's implementations. And it still leaves the attestation badness in place.
-
Passkey marketing is lying to you (it's simple)
Oof, I found a whole ton of anti-open-source-software quotes on the related Github issue https://github.com/keepassxreboot/keepassxc/issues/10406 :
> When required, the authenticator must perform user verification (PIN, biometric, or some other unlock mechanism). If this is not possible, the authenticator should not handle the request.
> [A passkey provider certification process] is currently being defined and is almost complete.
> This implementation is not spec compliant and has the potential to be blocked by relying parties.
> Then you should require its use when passkeys are enabled ... [You may be blocked because] you have a passkey provider that is known to not be spec compliant.
> I suspect we'll see [biometrics] required by regulation in some geo-regions.
> I see a lot of misinformation and incorrect guesses about the intentions of various parties in the recent threads. If it would be helpful, I'm willing to have a [private, non-public] call with interested parties to try and answer some of the questions that have been raised to ensure we have a common technical understanding of FIDO/WebAuthn.
I felt reasonably positive about Passkeys while writing this blog post, but continuing to read the spec authors' insistence that only Big Tech may handle these problems is extremely worrying. I really want to like this feature, but the authors are acting like complete jerks and driving me away.
-
Passkey technology is elegant, but it's most definitely not usable security
One of the Passkeys/WebAuthn spec people made a huge fuss over how KeePassXC did their export function https://github.com/keepassxreboot/keepassxc/issues/10407
-
Microsoft Confirms Password Deletion for 1B Users
By using the built in device attestation feature to blackball any passkey providers that allow that, apparently:
https://github.com/keepassxreboot/keepassxc/issues/10407#iss...
Now imagine a whitelist of acceptable providers. Suddenly, you don't even own your credentials anymore.
-
Concerns Raised over Bitwarden Moving Further Away from Open-Source
KeepassXC.
https://keepassxc.org/
Recently switched over from a premium Bitwarden account to it. Import from Bitwarden was a breeze.
Note that KeepassXC only writes to a local encrypted db file. Syncing that across devices is left to you. I used Syncthing for that.
-
FIDO Alliance publishes new spec to let users move Passkeys across providers
Should be noted that there's still debate on user presence, to the point that someone submitted a CVE[0][1] on KeePassXC for not abiding by this part of the protocol (and which I take Keepass's side).
[0] https://github.com/keepassxreboot/keepassxc/issues/9339
[1] https://keepassxc.org/blog/2023-06-20-cve-202335866/
-
Ask HN: AWS registering MFA will be required in 29 days
At Linux, I manage local 2FA with Numberstation GUI. It can import export.
sudo apt install numberstation
I manage passwords with KeepassXC
sudo apt install keepassxc
There is also newer version with additional features:
https://github.com/keepassxreboot/keepassxc
-
A note from our sponsor - InfluxDB
influxdata.com | 24 Apr 2025
Stats
keepassxreboot/keepassxc is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of keepassxc is C++.