>Set up the 1Password 8 desktop app That will be the Electron version. No thanks.
From the article: "Our new 1Password apps are built in Rust..." Maybe give this version a try then?
That's only the backend. GP's complaint is about the frontend.
1Password for SSH and Git (Beta)
41–50 of 406 posts
Re: 1Password for SSH and Git (Beta)
#42>Set up the 1Password 8 desktop app That will be the Electron version. No thanks.
I don't get the hate on Electron. Is it often bloated? Yes, sure. Has it allowed some of these excellent third party apps to make the move to Linux? Absolutely. I've been utterly surprised and excited by how much better 1Password has gotten over the last two years on Linux. We're seeing real parity with the OSX side of the house. Would I love native apps? Again, sure. But I really don't care. It runs pretty fast on m…
Because the idea of shipping a goddamn browser for each and every little GUI app is revolting and disturbing. What other crazy decisions have these people made?!
Re: 1Password for SSH and Git (Beta)
#43For those not buying into 1password, what is the "correct" non-1password way to manage SSH keys?
SSH keys authenticate you. They are an identity. You probably don't need more than one or two identities (maybe personal and work). You can just get a couple of YubiKeys and configure the OpenPGP applet, or the PIV applet, with an authentication key/certificate and use that for SSH. Take the token with you and you've got some pretty strong authentication.
More modern SSH servers will let you use U2F security keys in the same way, which are cheaper than the full YubiKey.
I've learned recently that YubiKey has really good documentation for how to set up their tokens to achieve different goals, it would be worth reading their docs if you're considering getting a hardware token for your keys.
Re: 1Password for SSH and Git (Beta)
#44Earlier quoted context omitted.
A mix. Typically I'll use one key per machine and add those keys in the places they need to be. This is good as you're reasonably well protected if that machine gets lost or stolen. The nature of public key cryptography means there's no risk associated with handing over your public key to many different places. However sometimes it's practical to use the same (private) key in multiple places. I do this for access to…
There is a slight risk - if someone has your public key they can setup a MITM server and pretend to be the one you’re expecting - and watch what you’re doing, or redirect test to production or similar. It’s really very minor and ssh itself should warn that the servers fingerprint changed.
Well they don't need your public key as well to do that kind of MITM so not sure thats really relevant.
Re: 1Password for SSH and Git (Beta)
#45It looks like 2fa is not required for 1password, and also that even if you did enable 2fa you can only use TOTP. Both TOTP and passwords are vulnerable to phishing as there's no cryptographic protocol going on there, you are just typing in the numbers from your phone. This seems like an excellent way to ensure that you reduce the security of your SSH login to either having a single-factor (password) or at best single…
Whenever I hear "oh but this 2FA is vulnerable to phishing" then why did security people annoy everybody and pushed for it before considering this factor?
I'm happy to use only a password for some sensitive things, because I can remember it.
Of course security is a spectrum and 2fa does help for a lot of stuff. Especially against websites that don't know how to hash your passwords properly (usually the ones from where passwords leak the most).
Re: 1Password for SSH and Git (Beta)
#46Earlier quoted context omitted.
I don't get the hate on Electron. Is it often bloated? Yes, sure. Has it allowed some of these excellent third party apps to make the move to Linux? Absolutely. I've been utterly surprised and excited by how much better 1Password has gotten over the last two years on Linux. We're seeing real parity with the OSX side of the house. Would I love native apps? Again, sure. But I really don't care. It runs pretty fast on m…
Because the idea of shipping a goddamn browser for each and every little GUI app is revolting and disturbing. What other crazy decisions have these people made?!
How is it different than using a GUI framework like Qt or GTK?
Re: 1Password for SSH and Git (Beta)
#47Ah neat, the app exposes an ssh agent socket: export SSH_AUTH_SOCK=~/.1password/agent.sock So you would essentially replace Keychain, Gnome-keyring, or the vanilla SSH-agent with 1password. Very nice solution.
Doesn't this give 1Password root on the universe?
That's a general theme I see with all this SSO stuff. You have a few companies with root on the universe. Am I weird that this concerns me?
Re: 1Password for SSH and Git (Beta)
#48My public ssh keys go quite a few places. I hope this can help me keep track of where I’ve uploaded my pubkey, since then revoking the pubkey is much more efficient. Or even do it for me, automagically.
Re: 1Password for SSH and Git (Beta)
#49>Set up the 1Password 8 desktop app That will be the Electron version. No thanks.
From the article: "Our new 1Password apps are built in Rust..." Maybe give this version a try then?
Unfortunately that's deceptive.
> This resultant application is hosted within Electron to ensure we have the exact same platform as our users.
https://www.reddit.com/r/1Password/comments/o0f9cl/were_the_...
Re: 1Password for SSH and Git (Beta)
#50Ah neat, the app exposes an ssh agent socket: export SSH_AUTH_SOCK=~/.1password/agent.sock So you would essentially replace Keychain, Gnome-keyring, or the vanilla SSH-agent with 1password. Very nice solution.
Not really into replacing vetted, well tested open source software with a proprietary app with cloud storage.