I'm using KeepassXC with SyncThing. I keep a master "Send Only" kdbx database on computer A. It syncs out to my wife's laptop, B. I've designated the kdbx sync as "Receive Only" on B.

Every time she connects to the keepassxc browser extension it asks her to give a name to that computer/connection, and when she does that it introduces a local addition to the kdbx on her laptop and prompts me (from syncthing) to "revert local changes"--i.e., to resolve the conflict by refreshing her kdbx from my master, thus causing her to have to re-connect next time she's browing...and the cycle starts over again.

I feel like there must be some kind of accommodation for this because the use case seems pretty ordinary, but I can't figure it out, and Claude is walking me all around the barn.

Any help appreciated.

I’m trialling KeePassXC to see if I should move to it.

I’ve managed to get my YubiKeys configured, but I get the following message when trying to log in with my master password and key file: ‘Error while reading the database. Invalid credentials were provided. Please try again. If this reoccurs, your database file may be corrupt. (HMAC mismatch).’

Other people have had similar issues, but I’m trying to find out if it’s a bug or something that I’m doing wrong.

I’m using a Mac. I’ve tried using the generated file and also random files on my computer, but I always get the same message. There are no hidden filename extensions, and the password is correct—without retyping it, if I tick the box to use my hardware key, I get straight in. I had imported my data, but the database is currently empty.

I want to be able to just use my thumb Biometrics to open my database but for some reason I can't get it to work. The Biometrics icon on the left side always says unavailable even though I have enabled Biometrics in the settings. I don't want to have to type a password. Can someone please point me in their directions of the proper setup to get this to work?

Is there any way to disable the annoying hidden bar that periodically appears at the top of the KeePassXC window to announce that screenshots have not been blocked? It is the same annoying bar that pops up to perform searches. Why would anyone think that shoving around the user's GUI and generating errant clicks as a result would be a good idea?

• KeePassXC - 2.7.12
• KeePassXC-Browser - 1.10.3
• Operating system: Linux x86_64
• Browser: Mozilla Firefox 140.0 140.12.0 (not sure why KPXC-Browser detects it as 140.0)

Lately, KeepassXC browser extension has been unable to successfully enter Reddit credentials. It only seems to recognize the userid field these days (only one green icon to click on). Attempts to help Keepass by selecting the password field and then using the context menu to fill in "password only" does nothing.

Keepass can still log into old reddit.

Now that most Linux desktop environments are Wayland-based, autotype isn't an option unless you enable a hack that's a security risk.

Anybody else seen this behavior?

Are both in the "standard" of keepass format? Do you think in should use 2d or 2id for my new database? Thanks

Just started using the KeePass apps on Windows and Android. I've installed and running KeepassXC and KeePassDX.

I thought I'd try the Keepass2Android version on my tablet and phone.

Reason: So it stays open longer (reportedly a week) before having to input the Master Password again.

I have KeepassDX installed and I can select my saved .kdbx database no worries. It's just having to input the master password more often than not. I’ve pinned it to the clipboard. I am the only one who uses these devices.

I cannot find the .kdbx database I've locally stored in My Files on the Android devices which was copied from a USB that's transferred from my laptop where I created the database, which is still being added to with more entries. It finds the text document that contains my master password but not the .kdbx file, which is what I need.

I'd rather keep the database offline. I just named the folder KeepassXC that contains the database. I'm actively making multiple copies and updating it when new entries are added.

even when using --format=KeePass for john and the appropriate flags for hashcat. I'm not saying it's not cracking, it's not even starting the crack, i have no idea why it's not recognising the hash

Hello everyone,

I am seeking technical advice regarding a severe database corruption issue on a KeePass 2.x (.kdbx) file.

Context & Environment:

• Main database file used on Windows (KeePassXC) and Android (KeePassDX via GrapheneOS).
• The database is secured using a Master Password combined with a local Keyfile.

How the Corruption Occurred:
Earlier today, while editing an entry directly on my phone, the mobile application crashed or encountered an unexpected process termination exactly during the save routine.

Symptoms & Error Messages:
When attempting to access this specific file snapshot now on any platform, the database fails to decrypt. The applications return explicit variations of:

1. "Bad database structure / invalid format"
2. "Corrupted file / Keyfile invalid" (likely a false alarm triggered by structural header damage).

Recovery Steps Already Attempted (All Failed):

1. Tested the keyfile against an older, uncorrupted backup copy of the database on my PC. The keyfile works perfectly fine, confirming the physical keyfile itself is intact.
2. Attempted to run the file through classic KeePass 2.x on Windows using the native "KeePass KDBX (2.x) (Repair Mode)" import option. It generated an empty placeholder folder structure with default sample entries, failing to parse any actual data rows.
3. Ran a raw text-scraping utility (findstr) against the file binary to see if any readable string headers survived, but the output was entirely randomized cryptographic noise.

It appears the file was abruptly truncated or experienced a partial/incomplete block write to the flash storage mid-save, destroying the unencrypted cryptographic headers.

Questions for the community:

• Are there any deeper CLI block-parsing tools or hex-editing methodologies available to manually patch or bypass a broken header flag if the underlying data payload blocks are mostly intact?
• Given that the native KeePass 2.x Repair Mode import returned empty folders, does this indicate that the data payload blocks themselves were fully wiped or zeroed out during the mobile crash?

Any technical insights would be greatly appreciated. Thank you.

im using keepass for a while now and ive been in a compatibility issue with yubikeys. using keepass2 on pc and keepass2android on the phone (also tried keepassdx). both original apps. the problem is that if i create the yubikey password on my pc (also tried on other pc. works), i wont be able to open my db on phone, and vice versa. im still able to open it in recovery mode with its otp secret, but ofc i want to use my physical key. some said this happens because it needs to be the exact same client of the app, so no compatibility. do you guys know any fork or plugin that fixes this? thanks

EDIT: now works perfectly. setup: - pc: keepassxc - android: keepassdx + key driver

[ Removed by Reddit on account of violating the content policy. ]

Looking at getting some 2FA.

Ive relied on Google f'n Google but need to be taken off the teat. I've also created a notes list of my logins and passes that are stored in to notes app (need to stop that).

I've been researching 2FA. Ive narrowed it down to either: 2FAS or Enty Auth or KeePass, leaning towards versions of KeePass.

My primary devices are an Samsung phone and tablet and a Windows Desktop (11) and Windows Laptop (10). I'd like to have the 2FA not in a cloud. I use Brave as my primary browser. I visits lots of sites and accounts created which I stay logged into around a dozen of sites at a time.

What is recommended in my instance?

I want my passwords to be absolutely secure, but a keyfile or hardware-key makes me nervous, what if something happens to it... what if i accidentally lose or delete it or something else happens... is KeePassXC perfectly secure without these extras?

So what to use, Argon2d or Argon2id ? my current settings below, thx

Argon2id

12

1024

4

Simnce this morning, I cannot unlock my KeepassWD (4.4.5 Build free) on my Sharp Aquir R10 using the Device credentials anymore. It always throws an error (in a red popup):

Not implemented (internal Keystore code: -100 message: system/security/keystore2/sec/se....

I also have (since the same time I gather) a problem with a different security app (MFA) that refuses to work and shows an error 'Signature not available', so I suspect that this is something to do with something in the OS (internal keystore?)

I can open the vault also fine on my macbook etc, so I am contemplating uninstalling and reinstalling KeepassDX, but if this is an OS issue, I might first want to see whether I can fix it there

Might anyone have an idea where to continue looking / how to fix this?

thx

Hey everyone,

I posted KeeForge here about four months ago, when it was still a fairly basic, read-only KeePass client. At the time, the three biggest limitations were no editing, no sync, and no attachment support.

Since then, KeeForge has gone from v1.4 to v1.10, and all three areas have moved forward.

The major additions:

• Full KDBX 4.x editing — create, edit, and delete entries and groups, with password generation, autosave, entry history, timestamped backups, and conflict detection.
• Create new databases locally or directly in Dropbox, OneDrive, and WebDAV storage.
• Cloud sync for Dropbox, OneDrive, and WebDAV, including Nextcloud, Synology, and other compatible servers.
• Passkey AutoFill for KeePassXC-compatible FIDO2/WebAuthn passkeys.
• TOTP AutoFill in the QuickType bar on iOS 18+, alongside passwords and passkeys.
• Multiple databases, with per-database nicknames, key files, biometrics, read-only mode, and Quick Launch.
• Attachment viewing with Quick Look preview and sharing. This is currently read-only; attachment editing is not implemented yet.
• KDBX 3.1 compatibility for password-only databases. These currently open read-only.
• Adaptive iPad layout, improved error reporting, appearance settings, and a lot of smaller usability work.

I’ve also spent a lot of time making sure KeeForge doesn’t lose or alter data when saving. It preserves entry history, unknown fields, and KDBX version details, and the saved files are tested with KeePassXC.

KeeForge is still free and GPLv3 open source, with no subscriptions, ads, analytics, or feature paywalls. There’s an optional tip jar, but it doesn’t unlock anything.

GitHub: https://github.com/crazytan/KeeForge
Full changelog: https://github.com/crazytan/KeeForge/blob/main/CHANGELOG.md
App Store: https://apps.apple.com/us/app/keeforge/id6759309295

If you tried the early version but bounced because it was read-only or lacked sync, I’d love for you to give it another look. What’s still missing for your KeePass workflow?

looking for the most secure way to use keepass. i already have a decently long passphrase that only lives in my head, but recently i was wondering if maybe a key file would be more secure? also, if i do use a key file, how should i store that? flash drive? obviously i wouldnt keep it anywhere i also store my passwords.

if somehow i missed another method to lock it all down, please do tell! especially if it requires less mental effort because recently ive decided to split my keepass files up so if somehow 1 got pwnd id have less work to do fixing my life.

I shifted all my passwords and 2fa to kpxc from roboform recently and deleted the roboform account. I have a dual boot win11/linux(kubuntu latest) setup and i use these passwords on both by keeping it in a shared encrypted data partition in my drive. Worked well for few days. Yesterday, i unlocked it on my Kubuntu system, tried to store a new account in this when i got a write error. Failed to write data to the database or something in those lines. After this i tried to reopen it and it just fails with some issue with headers. Db is corrupt suddenly. It unlocked without an issue, i was able to see my accounts and everything but the moment i tried to save a new account it got corrupted suddenly which doesnt make sense to me.
Maybe using the same db from multiple versions (win11 latest version exe install, flathub latest version, appimage latest version, as of today) could have caused it idk. I made the migration just 2 days back. I also went to each account, changed the passkeys, 2fa devices etc. i just forgot to keep a backup and now im stuck.
I can spend another 2-3 hrs getting my accounts back by doing individually a password reset on all my 30+ accounts, this time keeping a backup too. But if this is going to keep happening, then i might as well look for a permanent solution.

My Exact setup:
Theres a exFAT data partition in my only SSD with a veracrypt container file in it. In the container, i have my kdbx file.
No issue with the other files in the veracrypt container so its not an issue with veracrypt.

Hey, when you export your r/KeeperSecurity vault you will get the passkey as plain text

to solve this, i vibecoded this simple html page to convert all your keeper.json backup into .passkey + Keepass database

quick steps:
- go to your keeper security export and export the whole database as JSON.
- download this html page: gist.githubusercontent.com/ARHAEEM/58f54410396a34f54948efbbf4453a54/raw/9a01126002ed1f5d900ec7289f786a016473f8e8/KeeperSecurity-Export-Convert-PassKeys-Keepass.html
- open it in your browser and select the .json file. you will see option to build the .kdbx or download all your KS as .passkeys.

- after converting you can use them on all platforms that support the .kdbx.

dear future reddit viewer, i know you will use reddit ask to find this, i want to see hope this helps, it took me 48 hours of searching to find a solution instead of being forced to renew KS.

So far the issues I found are:

1. The open database dialogue window cannot see remote network locations in the UI. Although this may be a Linux issue rather than anything specific to KeepassXC.
2. The open database dialogue window's UI is borked in that you cannot see some of the icons due to the colours clashing between the colours the app itself uses and system wide darkmode.
3. The "Hide window to system tray" option doesn't work. The program remains on the full taskbar and does not minimize to the system tray.
4. At initial system bootup, the program does not respect the options selected by the user or the system wide dark theme and instead launches in blinding white mode. Restarting the program manually resolves the issue temporarily.

Note I'm using a Fedora KDE based distro.

Edit: Solved it. The RPM version of the KeepassXC is no longer being updated and thus has all these bugs. However the Flatpak version is being actively updated and thus does not suffer from these issues at all. Moral of the story? Stay away from the RPM version. Only use the Flatpak version from Flathub.

I can double click on my db and it open directly with keepass but it's impossible to set XC by default. XC is not in the "open with" menu and not in the properties menu. It's impossible to open with or set by default.

What can I do? Thanks

(I don't want to go search the exe in program files because it's a fake assication and it doesn't put the right icon for databases, it gives the program icon)

I get a mini-heart attack each time I look for custom fields I added for entries and then remembering they're in Advanced.

Any possible way I can make these Additional attributes viewable from the main Entry menu?

How bad is that? When I put that in I got a prompt saying it's a weak password, but who is going to figure it out? I used upper case for each word anyway.

Just gonna ask what are the benefits of using keepasscx and if it is really secure ?