alexeyd1000@lemm.ee to Showerthoughts@lemmy.world · 1 year agoNow that we are all switching to Lemmy, now is the time for all the redditors with embarrassing usernames to make their username right! Don't screw up this time!message-squaremessage-square572fedilinkarrow-up11.85Karrow-down174
arrow-up11.78Karrow-down1message-squareNow that we are all switching to Lemmy, now is the time for all the redditors with embarrassing usernames to make their username right! Don't screw up this time!alexeyd1000@lemm.ee to Showerthoughts@lemmy.world · 1 year agomessage-square572fedilink
minus-squareenoent@lemmy.ilwwbs.comlinkfedilinkarrow-up1·1 year agoLemmy uses a SHA256 digest for its TOTP codes. Basically every other service (and therefore most authenticator apps) use SHA1. So although you provide the right secret, you get a different code because it’s derived from a different hashing mechanism
minus-squarekamek@lemmy.fmhy.mllinkfedilinkarrow-up1·1 year agoOoooh ok cool. Sadly I’m using MS Authenticator so I can’t specify the type. I really don’t want to migrate to another one so hopefully this gets fixed I know there is a ticket open on github.
Lemmy uses a SHA256 digest for its TOTP codes.
Basically every other service (and therefore most authenticator apps) use SHA1.
So although you provide the right secret, you get a different code because it’s derived from a different hashing mechanism
Ooooh ok cool. Sadly I’m using MS Authenticator so I can’t specify the type. I really don’t want to migrate to another one so hopefully this gets fixed I know there is a ticket open on github.