Android-Password-S VS gopass

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.

én gopassolok, de same-same

use a password manager, seriously. I know my setup is overkill, but I've been rocking the yubikey/gopass combo for like 3-4 years now.

Depend on the kind of keys or secrets in general, and the infrastructure you work with. As bare minimum KeePassX/KeePassXC works as personal keys vault (that have a master password), GoPass (+git) as team passwords repository that use GPG keys as encryption, and passphrase for SSH keys. And, of course, trying to be mindful in what I run in my local computer.

Thank you for the details, and pointer to a solution. I've just installed gopass.

I also (in looking through other threads) found https://github.com/gopasspw/gopass and by reading the code learned how TOTP works.

I use gopass, because it is pass compliant and supports multiple recipients / teams which was my initial usecase for it. Just ask if you have any questions about my usage of it!

I'm currently using passwordstore/gopass for password management. It uses my GPG key to encrypt the passwords. The GPG key lives only only my Yubikey. The Yubikey requires a touch for each decryption.

That's true, the simple & fast UI (TUI/GUI) helps a lot. However, I would not extrapolate it to a huge problem. I am person, who have written own pass/passage implementation [0], just because I disliked how many steps I need to make to select the password for the form input, modify it or sync secrets.

Initially, I had used the `gopass`. It is probably the most convenient way to start using the password-store. It is cross-platform, 100% compatible with pass & pass-otp. To copy the password, you basically type the part of the file you are looking for. If you type "gopass show github", it will display a TUI, where you can select the file you are looking for (let's say you have two files "personal/github.com.gpg" and "work/github.com.gpg"). Unfortunately, the search function was far from perfect, and it had a problem with typos like "gtihbu" at the time, when I was using it.

To get rid of this issue, I decided to adapt pass/gopass to use `fzf` [2]. In the same time, my .password-store/ dir was rapidly growing that made me think about implementing pass from scratch. I improved the implementation to have better caching, synchronization between machines/mobile, but more importantly - a simple `secret [arg]` command that will execute `fzf` to list all known creds and simplify selection of the password. Of course, it accepted an argument that was limiting the results, which is great when you need to get back to the previous credential to retype something.

The introduction of `fzf` made it really convenient, and I decided to add more commands with fuzzy search, such as:

- `otp` - limits results files containing TOTP/HOTP token, calculates and copies it to the clipboard.

- `secret-edit`, `secret-remove`, `secret-show`... aliases to sub-commands that open `fzf` command in multi-selection mode, so by utilizing space key I could select what files are meant to be modified, removed, displayed etc. Quite handy for mass-edit.

- `secret-qr` - similar to the gopass' feature, but it made a simplified way to create and display QR codes dedicated to share contacts, WiFI SSID+password combination (etc.) to someone who was asking for creds from me.

Awesome, but alt-tabbing got me annoyed after a few years of using. I started pursuing for more sophisticated interface. I decided to give `rofi` [3] a try. I managed to fork that repo and also adapt to my convention of using password-store, but I left i3 for a macOS.

Currently, I have started working on a browser extension that takes care of suggesting password-store creds (based on the path, input parameters, location on the website etc.) similarly to what uBlock Origin does. That configuration is passed to my pass implementation, so on the github.com, my browser have only "work" and "personal" auto-suggestion, when I am focusing the text input.

I plan to create a similar app to Shortcat [4], but it will preserve the information what password has been asked for the focused app. I think, with VoiceOver assistance, it is more than possible to mitigate the need for alt-tabbing to the terminal for electron/native apps.

[0]: It is a private repository, maybe when it will be polished enough I will open-source it.

[1]: https://github.com/gopasspw/gopass

[2]: https://github.com/junegunn/fzf

[3]: https://github.com/alecdwm/pass-rofi-gui

[4]: https://shortcat.app/

gopass is what I've used for a long time. I like how it interfaces with the yubikey/gpg and how password stores can be held in a git repo. There are browser interfaces and GUIs for it but I tend to use it from the command line most of the time.

gopass :)

I wrote my own secret manager: safe. It stores your secrets as encrypted files on your disk (like pass and gopass), and is accessible from the command line. It differs from them in that you only need a master password to use it (so no GPG keys to manage). It comes with an agent (like ssh-agent) that can store your encryption key in memory to avoid typing your master password over and over.