E.g., with 1Password you can only setup regular “old” TOTP as an alternative and therefore backup (note you can use your Yubikey for both U2F and TOTP and other things too - this is where people get confused). RE: backup, yes, ideally you want to always register two but that’s not always possible. Others e.g., 1Password don’t (you can only register one). A correct authentication in part signs that challenge, so timestamping is irrelevant here, your answers are either fresh or they're invalid anyway.īecause a physical FIDO authenticator is independent from the computer you are not necessarily "done for" if the computer is compromised, unless you've outfitted your computer with a finger to press keys it cannot, for example, press the button on the key, so there is no way for the compromised computer to obtain signatures from the authenticator with the UP (User Present) bit set, and checking UP in the signed response is part of WebAuthn.Yep, some sites/services e.g., Google allow you register multiple security keys (for use with U2F). The Relying Party (a web site you want to authenticate to) sends a random challenge. If your root is compromised you're also done for.įor WebAuthn (and its predecessor U2F) none of this is correct. Also, it is probably possible to get the time-stamp within the kernel. The question is then: does timestamping the response reduce the attack surface enough compared to the downsides? I'd argue yes since the described attack can offset a failed login and the actual attack after a MITM. The verification process takes place at authentication so that would just tell you the current time, something you already know, it's useless. But these OTP strings are generated by the Yubikey, not by Yubico so there's no way for them to be "signed" in this way. Just have yubikey sign the current time, you're already trusting them to correctly verify the key string.īy "them" you presumably mean Yubico not the Yubikey.
0 kommentar(er)
