@mnw Thanks for the feedback.

I keep a master copy on a server hosted at my house. This also makes it easy to share a password database with my wife (encrypted with both my key and a key I generated for her). But I just have her open it with Emacs over SSH, which decrypts it automatically. Obviously there are more risks associated with that, but it's easy for her to manage, meaning she'll actually use it (it's an Org mode document).

Regarding trust: you don't need to trust the host if we change the pipeline a little bit. If you just run `ssh your-host cat db.gpg | gpg --decrypt | ...`, the plaintext is never visible to the server because it's decrypted client-side. This uses more bandwidth, but it means that you can host it anywhere. Also note that if your device is compromised, it'll have access to the entire plaintext of the database.

Just be mindful that you'll have to make sure you choose a strong passphrase or use a randomly generated symmetric key that you store on your local device. If you're using asymmetric encryption, then your database may become compromised in the future, which may or may not matter depending on the secrets. For example, I don't think GnuPG supports any post-quantum secure asymmetric algorithms yet (and they're still an area of research), but maybe other command line utilities do.