[conspire] (forw) You're one of 31, 081, 179 people pwned in the Internet Archive data breach

[Rick Moen]

Quoting Ivan Sergio Borgonovo (mail at webthatworks.it):

> Unfortunately KeePassXC can't be centralized and the DB can't be
> shared across devices.

It indeed doesn't do that.  Whether the deliberately simple model is
unfortunate is a matter of opinion.  If, hypotehtically, you wanted to
have a master *.kdbx password database file that then somehow is
read/written in local remote copies by multiple user-owned hosts,
solving that severe headache of concurrency and updating issues would be
the user's problem (and probably not even a tiny bit practical, if it
can be done at all).

I personally greatly appreciate the simplicity.  I don't need live
updating on multiple hosts of mine.  I could imagine using an
occasionally refreshed copy in read-only mode on the 2nd and additional
hosts, maintaining the database only on the master host, but have no
need for even that, at present -- and am happy to simply have an
excellent local file manager using a de-facto standard backing store.

> Is there anything open, that can be self-hosted and has good
> integration with browsers and android?

Quite possibly.  Not a use-case I've investigated, sorry.

For the record, I am lastingly leery of "integration with browsers":
That is available in KeePassXC but is not enabled by default.  I prefer
the tighter and smaller attack surface of using a password manager with
no such integration.

Also, I personally do not really trust my smartphone at all, and do
absolutely nothing security-sensitive on it.  And therefore do not seek
to store passowrds there.

Views Do Differ.[tm]