(no title)
irl_ | 4 years ago
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-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/
lkurtz|4 years ago
irl_|4 years ago
deviantintegral|4 years ago
https://support.1password.com/secret-key-security/
raverbashing|4 years ago
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).
Method5440|4 years ago
gonehome|4 years ago
dhess|4 years ago
However, for those reading along, initially the 1Password web interface for my account only offered the choice of setting up a TOTP authenticator. I completed that, and still saw no option for enabling a FIDO/YubiKey device. I then went into the 2FA settings for my account, toggled the option for YubiKey support off and then on again, and returned to the 2FA settings page. Only then did I see the option to enable a YubiKey.
I was then able to add my YubiKey and I can confirm that it's working with my 1Password account as a 2FA source.
irl_|4 years ago
At that point though, you already have a hardware token capable of holding SSH keys, so I'm still not convinced of the benefit.
electroly|4 years ago