If you pick option 3, where username/password/2fa are all verified at the same time, the interface for doing this is misleading.
In exchange for preventing username enumeration, it confuses users.
Users on the account help forums are regularly confused what their accounts are called, (they change their display name and think the username has changed, they change email and think the login name has changed, etc). The system that prevents knowing usernames exists only works by pretending every username exists, so it's a support burden. How do you help users sending recovery requests for what they think is their account, but doesn't actually exist?
Similarly, asking whether an account even has 2FA is a support burden, a user might not realise a hacker has set 2FA, a user might forget they have set 2FA, a user might not even know what 2FA is, they might not understand what clicking the button means, or enter random values, no other service asks for 2FA if you don't have it.
Basically, the option I propose which fixes all of 0wnage's problems, does it by creating other problems in terms of the user interface that confuses users and leads to more problems itself.
Everything is a tradeoff.
Sticking with just the OSRS or RS3 style approach, I'm adamant than OSRS's is better. I appreciate you disagree though, and can understand why, but I think the concerns of DOS are treatable seperately via other policies such as blacklisting networks (which does already happen).
15-Nov-2020 19:32:39
- Last edited on
15-Nov-2020 19:34:55
by
Hmm