What does HackerNews think of passforios?

Pass for iOS - an iOS client compatible with Pass command line application.

Language: Swift

#4 in Swift
Yes you can, you can use the https://github.com/mssun/passforios app which as of over a year ago supports Yubikeys.

The UX of having to grab your Yubikey every time is a bit clunky though (although that is limitation of the security key medium itself rather than the app).

https://github.com/mssun/passforios which also uses the safari password manager flow so its pretty seamless
Anyone considering pass (https://www.passwordstore.org/)? It is written in bash and uses gpg to store credetials on disk. And it is developed by the same guy behind wireguard. Also completely FOSS. On iOS I use passforios (https://github.com/mssun/passforios) and on macOS I am the developer of Pass for macOS (https://github.com/adur1990/Pass-for-macOS) which is a wrapoer for pass containing a Safari extension. Sync across devices is done using git (or cloud drives if you prefer). I use this setup for multiple years now and it works really well.
The UX of the pass iOS app [1] vs. the Android app [2] (especially the need for OpenKeychain on Android) is the main reason keeping me on iOS.

[1] https://github.com/mssun/passforios

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

Pass works great for me on iOS for years now and it's open source too [0].

[0]: https://github.com/mssun/passforios

For those who have concern about security, pass (https://www.passwordstore.org/) is a good alternative. It supports many clients like Pass for iOS (https://github.com/mssun/passforios), Password Store Android (https://github.com/android-password-store/Android-Password-S...). The good thing is that all are open source.
I think GPG keys get a lot of flack for not being the most user friendly thing and probably fair enough. The nature of them having to remain secret, makes managing them a bit confusing. I don't use mine for anything more than signing commits and (rarely) encrypting secrets

Personally, I use OpenKeychain[1] on Android, Kleopatra[2] on Linux, GPG Suite[3] on macOS and Pass[4] for iOS/iPadOS

Phew, that's a lotta apps but you can just pick and choose whatever you prefer. I have no idea about Windows myself. Once I imported my keys (public + private) into each application, I never really had to touch them again.

As I mentioned, I use my GPG key for signing my commits. I think I saved my password to my laptops keychain so it automatically signs my commits without my interaction.

Similarly, Pass automatically encrypts and decrypts everything without my interaction. Whether that's a good idea security wise aside, it works fairly seamlessly. Pass on my iPad is quite literally just a pull to refresh. I would have thought it'd be much more painful with all the GPG nonsense in play!

So, back to your questions:

> Does your setup require copying the same key to each device?

Yes but only once. It may also require entering your password anywhere from everytime to never depending on your settings. For my android device, I have to do it once every restart but after that, a process keeps my "store" open for example.

> What would happen if someone got your gpg key?

Presumably they could take all of my passwords and sign my Git commits as if they were me.

Personally, I have no strong investment in my GPG key, nor am I someone well known so this would have little to no effect beyond being a big annoyance. I would still own my email account so I'd still be able to reset the majority of my passwords.

Actually, I don't know my email password (since it's randomly generated) so I'd have to cross my fingers and hope the attacker hasn't revoked any of my sessions. Once again, no different than any other password manager. At least losing the key would be my fault, and not that of a third party I suppose.

> What would happen if you lost the key?

Presumably I'd lose all of my passwords but once again, that's no different than the single master password setup of those cloud based password managers.

I didn't realize until I looked it up just now but you can apparently generate a revocation certificate, separate from your key. From what it says on the tin, I imagine you can keep that safe and if you did lose your key, use it to tell any of the popular key servers that it's gone.

That wouldn't do anything to get your password back though, it would just signal to anyone looking up your key, that they shouldn't trust it.

Anyway, that was a bit of a tangent but the best way to learn is to just play around with GPG keys. The only reason I know the little I do is purely through making mistake :) I went through heaps of keys myself (I forget why) before I finally settled on my current one. You can even see some revoked ones here http://keys.gnupg.net/pks/lookup?search=marcus%40thingsima.d...

[1] https://www.openkeychain.org/ [2] https://www.openpgp.org/software/kleopatra/ and https://kde.org/applications/utilities/org.kde.kleopatra [3] https://gpgtools.org/ [4] https://github.com/mssun/passforios

For developers/tech-savvy people it is more or less perfect. I love the fact that it is based on git giving you a history and great control over synchronization. I use it to store all kinds of things such as passwords and files containing environment variables that can be sourced directly from the output of pass (source <(pass dotenv/project)). It even exists a great open-source iOS client: https://github.com/mssun/passforios
> The only downside is no access from my phone

For iOS: https://github.com/mssun/passforios works really well and it's open source.

There are a couple: https://github.com/davidjb/pass-ios https://github.com/mssun/passforios

Passforios is being actively developed and is shaping up well.