full-disclosure - Re: Google Accounts Security Vulnerability

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFhH=Nb2XVXiGnzrFOWu2MnZhQDfAm5wH_zUf7ioVwd2t5bZ_Q@mail.gmail.com>
Date: Sat, 19 May 2012 14:48:08 +0200
From: Mike Hearn <hearn@...gle.com>
To: coderman <coderman@...il.com>
Cc: full-disclosure@...ts.grok.org.uk, "Michael J. Gray" <mgray@...tcode.com>
Subject: Re: Google Accounts Security Vulnerability

>
> now if only Google's two factor auth could use tamper resistant tokens.
>  i trust my phone even less than my browser... :(
>

It can! The codes that 2-step uses can be generated using the open TOTP
standard, and the Google Authenticator smartphone app is just an
implementation of that:

  https://code.google.com/p/google-authenticator/

I don't know enough about hardware OTP tokens to say for sure, but I think
if you can find a time-based code generator you can probably set it up to
accept the same keys the smartphone app does.

Content of type "text/html" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/