News for hackers. Stuff that matters.
Re:Our Copyfish extension was stolen and adware-infested by userbinator on Sunday July 30, 2017 @06:38PM (#14888244)
The point of 2FA is challenge-response and the secret key is in the token. If a phishing site asks for 2FA it can get only one valid challenge-response pair, not the secret key.
Re:Our Copyfish extension was stolen and adware-infested by Gaelan on Sunday July 30, 2017 @07:15PM (#14888395)
One login is enough to authorize an Oauth app.
Re:Our Copyfish extension was stolen and adware-infested by ReverseCold on Monday July 31, 2017 @12:43AM (#14889513)
Require second login to transfer chrome apps to alternate account + 24 hour timer on transfer that sends an email to recovery email/everyone else relevant when extension is transferring.
Re:Our Copyfish extension was stolen and adware-infested by joshuamorton on Sunday July 30, 2017 @06:53PM (#14888298)
That still allows them to log in though.
Re:Our Copyfish extension was stolen and adware-infested by Buge on Monday July 31, 2017 @12:42AM (#14889508)
SMS and TOTP (Google Authenticator) can both be phished.

U2F cannot be phished.

Re:Our Copyfish extension was stolen and adware-infested by TeMPOraL on Monday July 31, 2017 @12:59AM (#14889564)
Can't it?

What if I control the user's computer and can let my own code interact with U2F? Or does the protocol somehow prevent that?

Re:Our Copyfish extension was stolen and adware-infested by Buge on Monday July 31, 2017 @01:59AM (#14889793)
If you control the user's computer, that isn't phishing. That's keylogging/credential theft.