commit - c99336885b66c2f9e58e98e65251398696904984
commit + ce5c430c3a55f79f3c9605dd8411c4933f48999d
blob - 162b8ae207737b592268871c40fe7fa3e07cd2f1
blob + e92aa41ac7f362866688b84923afb344feec728e
--- content/blog/password_managers.md
+++ content/blog/password_managers.md
KeePassXC has a few nice features, like scanning the password database against [HIBP](https://haveibeenpwned.com/) or Browser Integration (which felt mediocre at best).
The ultimate password management option for me is pass, though, which stores all passwords (and accompanying information) in single text files encrypted with [GPG](https://gnupg.org/). This makes it trivial to write scripts for use with pass, like [passmenu](https://git.zx2c4.com/password-store/tree/contrib/dmenu/passmenu), a script that allows easy copying of passwords through [dmenu](https://tools.suckless.org/dmenu/).
-The downside for using pass for me is similar to KeePass: Syncing across devices. This is usually mitigated by using git in combination, but this inevitably requires me setting up a repo _somewhere_ (either on a service like [Sourcehut](sourcehut.org) or on my own server), but this exposes the "database" to the internet, which makes me feel a little uneasy.
+The downside for using pass for me is similar to KeePass: Syncing across devices. This is usually mitigated by using git in combination, but this inevitably requires me setting up a repo _somewhere_ (either on a service like [Sourcehut](https://sourcehut.org) or on my own server), but this exposes the "database" to the internet, which makes me feel a little uneasy.
By far the most important "feature" I need is being able to access my passwords on my phone, though. All 3 options make this possible, but Bitwarden is by far the simplest option since the syncing is seamless, without the need to set up some synchronization.
Ultimately, this is the feature that pushed me to Bitwarden in the first place, but I am rethinking this decision and feel like either pass or KeePassXC is the way to go forward.
