this post was submitted on 22 Aug 2023
397 points (98.5% liked)

Technology

34920 readers
165 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.


Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.


Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago
MODERATORS
 

I personally am fine with this.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Xylight@lemmy.xylight.dev 17 points 1 year ago (1 children)

BTW, any authenticator app works when it tells you to use one. They all use a standard, so it doesn't matter which one you use.

[โ€“] tool@lemmy.world 3 points 1 year ago

BTW, any authenticator app works when it tells you to use one. They all use a standard, so it doesn't matter which one you use.

Eh, it's a little more nuanced than that, there're more standards for MFA code generation than just TOTP.

And even within the TOTP standard, there are options to adjust the code generation (timing, hash algorithm, # of characters in the generated code, etc.) that not all clients are going to support or will be user-configureable. Blizzard's Battle.net MFA is a good example of that.

If the code is just your basic 6-digit HMAC/SHA1 30-second code, yeah, odds are almost 100% that your client of choice will support it, but anything other than that I wouldn't automatically assume that it's going to work.