keepass

Well it sounds like you just did a security audit of KeePass, albeit an incomplete and cursory one.

KeePass just asks for a path to a password file, so you have to put it on shared storage.

That said, the author of KeePass responded to all the discussions here over on the project forum at SourceForge.

No, it's actually KeePass for Android that doesn't give you any other way to do this.

KeePass from version 1.24 & 2.20 (in 2012) use header authentication to prevent data corruption attacks.

However, for corporate use I must recommend siptrack, a Django-based webbapp with a xmlrpc gui that tries not so much to replace keepass but rather racktables and keepass.

I know that KeePass probably works best for family, so we may switch to that in the future.

I'd still use KeePass before I used LastPass, though, and would still use KeePass before I used no password manager!

I never claimed or implied that latest design of 1Pass repository is worse or even security-equivalent to KeePass.

KeePass is really good and user friendly, but like I said, is missing some things I need.

I have ample factual evidence that both KeePass and 1Pass authors had made multiple crypto blunders.

If you use four-five different password spread among different sites, they will be easier to break then any generated password from keepass, pass or passwordstore.

However, the points you mention pretty much force me to have a KeePass file for "those other passwords".

Master Password works very differently from 1Password, KeePass, LastPass, etc: "Master Password is a stateless password generator.

NET implementation to the "legacy" c version, Keepass 1.x.

I opted for setting up a.kdb KeePass file in a private git repo and giving everyone ("everyone" = myself + one other) access to that.

Keepass was never meant for corporate use, that much I am positive about.