Why every TOTP app default uses SHA-1 hash encryption?

https://lemmy.world/post/15130441

Why every TOTP app default uses SHA-1 hash encryption? - Lemmy.World

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?

It’s up to every individual website to use whatever specific type of hash function they want, so absent of really technical users that know how to change the cipher, they all just default to SHA-1 maximum compatibility.
And some TOTP apps don’t interpret the algorithm parameter correctly (ahem Google), which makes it safer to go with the default SHA-1.
Key Uri Format

Open source version of Google Authenticator (except the Android app) - google/google-authenticator

GitHub