News for hackers. Stuff that matters.
Re:Google: Security Keys Neutralized Employee Phishing by izacus on Monday July 23, 2018 @09:34AM (#17592584)
The key replaces the keycode of 2FA auth - password still has to be used.

You can already use the same process on your GMail if you have a compatible U2F key.

Re:Google: Security Keys Neutralized Employee Phishing by decasia on Monday July 23, 2018 @09:36AM (#17592609)
OK thanks, this clarifies the part that says "it began requiring all employees to use physical Security Keys in place of passwords and one-time codes," which I found super confusing.
Re:Google: Security Keys Neutralized Employee Phishing by ehsankia on Monday July 23, 2018 @01:27PM (#17594254)
Strange sentence, but I believe they mean replcaing "password + one time code" with "password + U2F"
Re:Google: Security Keys Neutralized Employee Phishing by Boulth on Monday July 23, 2018 @01:41PM (#17594356)
Actually U2F can be used to devise several different schemes, either token+password, or token alone, even just token without username. Of course each of these has various advantages and disadvantages.
Re:Google: Security Keys Neutralized Employee Phishing by cbhl on Monday July 23, 2018 @06:29PM (#17596548)
Some logins are cookie + security key (basically if I've already logged in today) which basically feels like "tap my security key and I'm logged in".

Of course, more sensitive stuff (access to production, access to pay stubs, access to $cloud_erp) requires re-entering password plus the security key.

Re:Google: Security Keys Neutralized Employee Phishing by Freak_NL on Monday July 23, 2018 @10:41AM (#17593073)
The password can be replaced by something simpler like a PIN, which is why you'll read about U2F replacing passwords and one-time codes.

Sometimes 'replacing passwords' is used to mean 'replacing the traditional username and password login' as well.