oath-toolkit-help
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[OATH-Toolkit-help] Bug#666185: Should accept base32 encoded keys


From: Martin Michlmayr
Subject: [OATH-Toolkit-help] Bug#666185: Should accept base32 encoded keys
Date: Sun, 1 Apr 2012 10:56:23 +0100
User-agent: Mutt/1.5.20 (2009-06-14)

* Simon Josefsson <address@hidden> [2012-04-01 11:17]:
> > oathtool currently requires an unencoded key.  It would be nice if it
> > would also accept base32 encoded keys, so you could pass it e.g. a key
> > from Google directly.
> 
> Hello.  Thanks for the report, it sounds like a good idea.  Please try
> just uploaded 1.12.0.

Thanks.  Unfortunately, I get:
| oathtool: base32 decoding failed: Base32 string is invalid

This is because my string is lowercase whereas oathtool expects it to
be uppercase (oathtool works fine if I convert it to uppercase).  My
understanding of base32 is that both upper and lower case is accepted.
(But I haven't actually read the standard.)

Anyway, thanks for implementing this!

-- 
Martin Michlmayr
http://www.cyrius.com/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]