3 ms·
Worth taking a moment to contemplate for second factors whether the credentials you have could "leak" like this. * For SMS 2FA you might leak the user's phone
by tialaramex 6y ago
Worth taking a moment to contemplate for second factors whether the credentials you have could "leak" like this.
* For SMS 2FA you might leak the user's phone number which isn't good, but even if you "leak" the 2FA code it's transient and will very quickly be worthless
* For TOTP leaking the current TOTP code (either entered by a user or calculated locally) is transient again, but if you instead leak the seed (which you have) that's fatal.
* For other types of single use codes leaking a code that was successfully presented isn't a problem (it was single use and now won't work) but leaking codes you've generated (e.g. from a "new codes" page) is fatal.
* With WebAuthn you (the relying party) do not have any secret credentials at all, so you can leak everything you have and it makes no difference to the system's security so long as you implemented it correctly.
- SahAssar 6y agoWith WebAuthN you do have secret credentials but if implemented correctly it is almost impossible to leak them, right? Also it might be worth mentioning that WebUSB implementation details have sometimes lead to issues/flaws with WebAuthN/u2f keys: https://www.wired.com/story/chrome-yubikey-phishing-webusb/ https://www.wired.com/story/chrome-yubikey-phishing-webusb/