I use Aegis as my 2fa. Today on new token creation I observed that there’s hash function set to SHA-1, later checked all my tokens and the result is same type of encryption used for all. So I have edited all my tokens to SHA-256 as a result my totp doesn’t authenticate. Do I have to rescan my tokens for updating to SHA-256 or it doesn’t work like that?

Security: SHA-1 < SHA-256 < SHA-512

Speed: SHA-1 > SHA-256 > SHA-512

My doubts are: Why can’t we use SHA-256? Is it because TOTP requires less time so faster one(SHA-1) is chosen? Can we use SHA-256 for TOTPs?

  • devfuuu@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    7 months ago

    I read the other day something about being a limitation that google official app only supports that and all the other are forced to use the same to be compatible.

    https://lobste.rs/s/gqoj5n/passkeys_shattered_dream#c_bv8hpr

    Also you can’t change it on your side, a server and the part tou have in your authenticator need to be in sync. There’s no point to change only on your side if the server was not configured to also use the same settings I guess.