search

JumpMaster / QuickAuth

Google Authenticator for the Pebble Smartwatch!
GNU General Public License v3.0
68 stars 23 forks source link

HOTP/T60 not supported #4

Closed squat0001 closed 9 years ago

squat0001 commented 10 years ago

Hi,

i wanted to use T60 instead of T30, because i have an Token too.

please :-)

thanks

JumpMaster commented 10 years ago

Sorry but I don't know what that is. Is it supported in Google Authenticators app? The current TOTP code is copy/pasted directly from Google's TOTP pam module. I can't promise I can deliver this but I'll try. Leaving this open! :)

squat0001 commented 10 years ago

your apps is doing HTOP/T30 (30 secounds), some hardware tokens use T60 (60 secounds).

google is using HTOP, which has an RFC.. and some hardware tokens is using that too..

http://www.ftsafe.com/product/otp/totp https://www.ietf.org/rfc/rfc4226.txt

and .. i used some of the c200 tokens on my own servers, so it would be very nice if they just work :-)

greetings

JumpMaster wrote:

Sorry but I don't know what that is. Is it supported in Google Authenticators app? The current TOTP code is copy/pasted directly from Google's TOTP pam module. I can't promise I can deliver this but I'll try. Leaving this open! :)

— Reply to this email directly or view it on GitHub https://github.com/JumpMaster/PebbleAuth/issues/4#issuecomment-37546801.

Florian Reitmeir E-Mail: florian@reitmeir.org Tel: +43 650 2661660

JumpMaster commented 10 years ago

So can this not be generated at all on Google Authenticator? The other option is counter based which involves manually generating a code and knowing what code number you've generated.

I'm guessing that isn't it. How are you currently generating codes for this platform? Also your link shows it's HMAC based where as the Google method is SHA based.