Live data from Hacker News

6 digit OTP for Two Factor Auth (2FA) is brute-forceable in 3 days

lukeplant.me.uk

41–42 of 42 posts

Re: 6 digit OTP for Two Factor Auth (2FA) is brute-forceable in 3 days

#41
post #7

This article is pointless clickbait - what percent of systems don't have some sort of throttling or lockout after X number of bad guesses - damn few I would say. Even the most basic, low budget systems I have developed or worked on have throttling rules in place - many with exponentially increasing timeouts that would prevent this sort of attack. If a website/system does not implement even the most basic security pra…

If there's a leak of valid usernames or email addresses, for a system that has a few million users, that has a lockout after 10 wrong guesses, then you could gain access to one account for every 10,000 lockouts.

> leak of valid usernames or email addresses

...and passwords, because OTP is the second factor.

Re: 6 digit OTP for Two Factor Auth (2FA) is brute-forceable in 3 days

#42

Earlier quoted context omitted.

> Its a shame the TOTP standard does nor support variable code length, 8 symbols seems to be better for high value accounts but still usable It does. TOTP (RFC 6238) builds off of HOTP (RFC 4226), which states (§5.3): > Implementations MUST extract a 6-digit code at a minimum and possibly 7 and 8-digit code. Depending on security requirements, Digit = 7 or more SHOULD be considered in order to extract a longer HOTP v…

True, but the problem is I do not believe any apps implementing TOTP allow for codes over six numerical digits. So the real world standard (Google Authenticator) does not support it.

Google supports 6 or 8, [Aegis](https://getaegis.app/) supports the full standard, Authy supports 6 or 8, Sophos supports 6 or 8. Lots of support.
Post reply on HN