Pass4Win VS Android-Password-S

I've been using pass for several years now and I recommend it to my friends, but I usually get weird looks when I say I store my passwords in a git repo (it's not as bad as it sounds!). Here's why:

- I host my git repo on my desktop computer (through SSH), so it's not exposed anywhere except if you have SSH access to my computer. (A lot of people seem to think git = GitHub which is not true).

- The passwords are GPG encrypted so even if it were leaked that would be okay as long as my secret key remains secure.

As far as usability goes, I usually use the -c option to copy/paste my passwords. I used a browser extension for awhile, but I haven't gotten around to reinstalling since the copy/paste works fine for me. Syncing with my phone and Linux devices works perfectly (since it's just git).

The Windows client seems to be no longer maintained [1], so I would like better support here for my Surface. But this is still okay since I can SSH to my desktop computer from Windows and copy/paste the passwords from there.

[1] https://github.com/mbos/Pass4Win#readme

There is no "database", it's just a bunch of GPG encrypted files synced with git.

For Android there is https://github.com/android-password-store/Android-Password-S....

For Windows the only thing (Pass4Win) i found is unmaintained.

See https://www.passwordstore.org/#other

These are the types of applications that I really love. It stores the data in a cloud service that already has enough free capacity for say a notes app. It's like how we can store pass(1) passwords on a git repository (Sync it with Github) and use that as the destination of Android Password Store[1], and you have a easy password manager.

[1] https://github.com/android-password-store/Android-Password-S...

Since I store most of my passwords using https://www.passwordstore.org/, I have used mobile with https://github.com/android-password-store/Android-Password-S.... I'm happy enough with it. Sucks for getting anything into consoles, for obvious reasons.

That's the exact setup I use on my main phone. There's also https://github.com/android-password-store/Android-Password-S..., which I use on throwaway phones.

I moved to pass cli (on i3 with a simple rofi selector) and the FOSS android app https://github.com/android-password-store/Android-Password-S... synced over Syncthing and I never look back

For encrypted secrets in git I'd suggest looking at sops and password store:

https://github.com/mozilla/sops

https://github.com/android-password-store/Android-Password-S...

Both are extremely useful secrets oriented git tools with support for things like PGP encryption. Both will encrypt with multiple keys too, making sharing relatively easy. The android pass app even manages SSH keys for pushing and pulling. There may be good inspiration in those repos, or even code you can borrow.

Also, thanks so much for making this: it is elegant and lovely. Keep it up!

In addition, plasma-pass, qtpass, android password store (https://github.com/android-password-store/Android-Password-S...) are nice as well. Throw in a NFC Yubikey and OpenKeychain on android, then you can lock them with hardware keys. Since pass uses git, syncing can be done to a private repo on your home network or even just a cheap usb stick.

Oh dammit. I have stopped using Gopass and started rewriting pass just for that reason - missing AGE encryption. At least I have learned something new and I feel better while my fuzzy finder UI instead of their TUI. However, big kudos to Gopass team for awesome work and really useful tool.

Before I start working on next project... Do you recognize any mobile app, which could replace PasswordStore.app for Android but with AGE support?

[0]: https://github.com/android-password-store/Android-Password-S...

I'm thinking about adding encrypted file support to my pass wrapper, p, but I've not really found a good argument to support breaking mobile apps (such as https://github.com/android-password-store/Android-Password-S...).

You'd have to manually look up the entries in a lookup table to resolve obfuscated names back to readable names... Or upstream support for whatever format is devised. I dunno.