On 05/05/2025 15:59, Marc SCHAEFER wrote:
Hello,Has anyone experienced the following setup: On a standard system (Debian GNU/Linux): - install keepassxc, create a master password and a database file [ alternative: keepass2, but mono dependancy ] - make sure that database file is on a git, pushable to a remote repository (I like git-on-SSH), and push/commit it when required On an Android phone: - install GitSync, and sync the above repository to a local directory - install KeePassAndroid, and use the database file on that directory Now, create the passwords and sync around. I have quickly tested, it it works (I tested with keepass2, but keepassxc should also work). Do you use setups like this? Or do you prefer cloud solutions like the ones offered by keepass2, or even a fully web (possibly mobile, too) solution like bitwarden (I already use it, but it's a bit complicated & has licencing issues)? Any inputs? Thank you.
You might like https://www.passwordstore.org/ which embraces the UNIX philosophy a bit more:
* Each password lives in a gpg-encrypted file, whose name is the title of the website or resource that requires the password * Each file is plain text, and can store additional meta data (such as a username) * The Pass CLI understands if the password store is a git repo and will add git commit messages with each edit. You can also do "pass git push" / "pass git push" to synchronise to another repository (GitHub if you want cloud, or perhaps a Forgejo instance you self-host?)There are, of course, apps for Android, or plugins for browsers as you see fit.
OpenPGP_signature.asc
Description: OpenPGP digital signature
