prs VS Android-Password-S

I created `prs` which solves a lot of painpoints I had with pass and other clients.

It is compatible with pass and uses the very same store.

https://github.com/timvisee/prs

Thanks for mentioning prs [1], dev here! :)

Yes it definitely meets those requirements, being written in Rust, supporting pass, TOTP, Tombs amongst other things.

Though its CLI is a bit different than classic pass. That is on purpose in fact, to achieve a better UX and less ambiguous commands.

[1]: https://github.com/timvisee/prs

prs has a hidden yeet to throw secrets/passwords away:

I've developed `prs` as `pass` alternative with many annoyances fixed for daily use. It provides automatic syncing between multiple devices through git, supports multiple keys and many other things. It simply uses your existing `pass` store.

Some might find it useful: https://github.com/timvisee/prs

I've added Wayland (clipboard) support to prs recently. It's a pass compatible client like gopass.

Terminal gurus might like what I've been working on lately:

https://github.com/timvisee/prs

Free and open-source, keep control in your own hands, forever. Encryption with gpg, sync with git. Compatible with pass, which means better support and easy migration.

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.