You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat: add sha256 and sha512 support
As the original implementation followed only RFC-4226, it had only SHA1
support. This covers a lot of tokens, but secure tokens are not SHA1, but
SHA2 based as described in RFC-6238.
Until now, I though only hardware tokens use SHA2 (SHA256, SHA512) and
maybe some edge cases, but not common. That was probably true almost 10
years ago when I originally created this tool. Today, even tho I didn't
see 256 or 512 tokens yet, I think it's more common, and soon they will
be used in a lot of places.
Resolves#133
References:
- #133
- https://www.ietf.org/rfc/rfc4226.txt
- https://www.ietf.org/rfc/rfc6238.txt
Signed-off-by: Victoria Nadasdi <victoria@efertone.me>
0 commit comments