The problem with that is the ordinary user doesn't want to have to run a server (indeed, most users may not have the foggiest clue how) in order to store their passwords locally. #Password managers do everyone a great disservice when they do not offer the option to store passwords in a database on the same computer the password manager runs on, with nothing extra for the user to set up. I believe that #KeePassXC may allow you to do this but since I am not using it (yet) I'm not certain.
RT from Steven J. Vaughan-Nichols (@sjvn) For password protection, dump #LastPass for #opensource Bitwarden https://theregister.com/2023/01/16/dump...
@Lunatech One thing I'm still not sure of is how to provide an executor with access contingent on death or incapacity. The best I can think of is to have a dead man's script send an unlock code to an encrypted key?
@Lunatech you are correct. #KeePassXC does, indeed, store data locally in an encrypted .kdbx file.
Synchronization requires another tool like #SyncThing or Drop Box, which amounts to running a server or trusting someone else's.
Of course, that then means it's the users responsibility to back the file up, preferably off site, because if it is lost or corrupted there is no recourse.