>Set up the 1Password 8 desktop app That will be the Electron version. No thanks.
1Password for SSH and Git (Beta)
21–30 of 406 posts
Re: 1Password for SSH and Git (Beta)
#22This 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-factor + TOTP, where you previously had a phishing-resistant cryptographic protocol.
Is this really an improvement for security, or is it just a usability improvement (i.e. sync of keys) intended to work around policies trying to improve security (i.e. required use of keys)?
(The other option is I skimmed the docs badly and maybe I've misunderstood something, it's possible.)
Edit: I did skim the docs badly, it is possible to use a FIDO2/WebAuthN key for 2FA. https://support.1password.com/security-key/
Re: 1Password for SSH and Git (Beta)
#23I’ve been treating SSH keys in the same way I would a password. Each service gets a new key generated for it. From doing some reading though it sounds like I might be wasting my time. Apparently it’s fine to have one key for an individual machine and to use that for everything. What’s everyone else’s take on that? Are you reusing a single key or generating each time?
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…
It’s really very minor and ssh itself should warn that the servers fingerprint changed.
Re: 1Password for SSH and Git (Beta)
#24I’ve been treating SSH keys in the same way I would a password. Each service gets a new key generated for it. From doing some reading though it sounds like I might be wasting my time. Apparently it’s fine to have one key for an individual machine and to use that for everything. What’s everyone else’s take on that? Are you reusing a single key or generating each time?
Re: 1Password for SSH and Git (Beta)
#25For those not buying into 1password, what is the "correct" non-1password way to manage SSH keys?
Re: 1Password for SSH and Git (Beta)
#26Now would it be possible to make something like this for GPG?
Re: 1Password for SSH and Git (Beta)
#27>Set up the 1Password 8 desktop app That will be the Electron version. No thanks.
Re: 1Password for SSH and Git (Beta)
#28>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…
Re: 1Password for SSH and Git (Beta)
#29>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…