News for hackers. Stuff that matters.
Re:Ask HN: Does anyone else think this 2FA everywhere is get... by warrenm on Friday March 18, 2022 @10:22AM (#30722608)
Nope

If anything, the codes should be longer - 8 digits would be far better (8-10 digits bumps up against what a person can easily keep in their mind at one time for long enough to type it)

Re:Ask HN: Does anyone else think this 2FA everywhere is get... by quaffapint on Friday March 18, 2022 @10:41AM (#30722885)
Per RFC (for HOTP, which is just TOTP w/o the time element)...

"The HOTP value must be at least a 6-digit value. It is also desirable that the HOTP value be 'numeric only' so that it can be easily entered on restricted devices such as phones."

6 was defaulted to in the TOTP for being 'secure enough' and easy enough for most people to remember.

Re:Ask HN: Does anyone else think this 2FA everywhere is get... by Spooky23 on Friday March 18, 2022 @11:01AM (#30723161)
Exactly, it’s a pragmatic choice.

There are scenarios where that doesn’t provide sufficient assurance, but those scenarios are also not really suited for TOTP in the first place!

Re:Ask HN: Does anyone else think this 2FA everywhere is get... by catskul2 on Friday March 18, 2022 @10:39AM (#30722854)
Why should the codes be longer? Is your concern brute force attacks on the code across a network connection on something that is attempt limited?
Re:Ask HN: Does anyone else think this 2FA everywhere is get... by warrenm on Wednesday March 23, 2022 @02:05PM (#30781412)
it's kind of interesting that physical totp generators like entrust, securid, etc all went with 8 digits vs the "typical" digital totp codes being 6 digits long

I'm not so much concerned with brute force as that 8 is better than 6

Re:Ask HN: Does anyone else think this 2FA everywhere is get... by i0nutzb on Friday March 18, 2022 @10:32AM (#30722759)
Not necessary _longer_ but could include letters too.