Add support for SHA-384 hash algorithm#1789
Add support for SHA-384 hash algorithm#1789sorooshm78 wants to merge 3 commits intobeemdevelopment:masterfrom
Conversation
alexbakker
left a comment
There was a problem hiding this comment.
We've previously closed #1679 because we couldn't find any services using SHA-384 for TOTP. Which service did you encounter that requires it?
|
Hi @alexbakker, Thanks for getting back to me. I encountered this requirement within our organization. We use a custom internal enterprise SSO and VPN gateway where the network administrators have specifically configured the TOTP generation to use Regarding your second question, as far as I know, Google Authenticator does not support I can completely revert the changes made to the .proto file (and related Google Auth migration code) and only keep the core SHA-384 implementation for Aegis itself. Let me know if you’d like me to update the PR! |
Thanks for the great app. I needed
SHA-384support for my use case, which wasn’t available inAegis, so I implemented it. Opening this PR so others can benefit as well.