r/KeePass

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.

🎉 10,000 downloads!

To celebrate, I'm giving away 100 Lifetime Premium codes.

1. Post Lockify on any social platform.

2. Tell me what you like about it.

3. First 100 participants win.

Many codes are already claimed.

Hurry! 🔐

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

• KeePassXC - 2.7.12
• KeePassXC-Browser - 1.10.3
• Operating system: Linux x86_64
• Browser: Mozilla Firefox 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

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?

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.

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?

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