-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update HMAC SHA #197
Comments
This is in progress, but as noted on #198 a number of popular OTP apps don't support SHA256 including: Microsoft Authenticator and Authy so it's probably not recommended unless you can control the apps being used to some extent. Given the location where the HMAC is generated there doesn't appear to be a big push or concern (it's only used to generate the time codes). |
Understood and agree with you regarding its isolated use. Interesting that some OTP apps don't support SHA256 yet. Microsoft Authenticator is one of my supported OTP apps. Thank you, Adam. |
Closing issue. |
Can SHA in GenerateHashedCode be updated from HMACSHA1 to HMACSHA256?
The text was updated successfully, but these errors were encountered: