Hey guys,
after talking about the RFCs and so, I couldn't stop to read them. ;)
There I stumbled about the test vectors. They are not working with the
aerogear-implementation, because of the Base32 encoding which is used by
the google authenticator.
The used secret in the rfc is "1234567890", which is not valid google,
because Base32 uses ABCDEFGHIJKLMNOPQRSTUVWXYZ234567.
vectors:
http://tools.ietf.org/html/rfc6238#appendix-B
Using the "reference implementation", which is provided in document the
generated token is different from aerogear one.
Is the plan to support the RFC or Google? (or better both? :))
--
Viele Grüße/Best Regards
Daniel Manzke