pass-tomb VS vaultwarden

By itself, Passwordstore will not encrypt file names or directory names, which might not be a problem if no one else has access to the machine that hosts your git repo, but if that's not the case (even if it's a private repo on whatever platform), you might want to use either Tomb or git-crypt-remote to have full end-to-end encryption. There are even some tools that glue tomb and pass together (https://github.com/roddhjav/pass-tomb for one), though I'm not sure what's the situation is like when it comes to mobile integration with tomb/git-crypt-remote.

That can of course be fixed by using pass-tomb, but that isn’t implemented in mobile clients (at least not on iOS).

- https://pujol.io/blog/tomb-with-gpg-keys/ - https://github.com/roddhjav/pass-tomb

A plug-in called pass-tomb exists to fix this, but doesn’t work with mobile apps (a least not iOS)

To people who want to self-host this, look at Vaultwarden which is a fully compatible alternate server with even more features:

https://github.com/dani-garcia/vaultwarden

Been running it for a year with 0 issues.

For passwords and 2FA I use Bitwarden in combination with a self-hosted Vaultwarden service (for imcreased security and use of pro features for free).

Vaultwarden as Password-Safe

I have a lot of software that I host myself on my home server, partly to save money but also because I want to control my own data. For example, I host VaultWarden which is the open source server for BitWarden. This gives me all the premium features for free with the added bonus of keeping my passwords out of the cloud.

Self hosting is incredibly easy with vaultwarden (https://github.com/dani-garcia/vaultwarden)

I have now switched to using the BitWarden app with the self-hosted VaultWarden server. I have set it up, so my passwords are only accessible when connected to my home network either physically or with a VPN (I am using tailscale for this).