4 ms·
On the login form thing: it's to prevent easy brute force attacks
by elisaado 8y ago
On the login form thing: it's to prevent easy brute force attacks
- JeanMarcS 8y agoIsn’t it a bit lazy on the developers side ? Limiting the number of errors before sending a link to reset your password (for example, I agree there might be different ways to deal with that) is no rocket science, and being dependent on third party for such a trivial thing is, in my opinion, a bad idea.
- dmurray 8y agoIt really isn't trivial. Rate limiting is great, but not enough. If you lock people out after a certain number of failed login attempts, you allow an adversary to DOS your users by constantly trying to log in as them.
- dpwm 8y ago> It really isn't trivial. Rate limiting is great, but not enough. Rate limiting alone isn't a solution. But it can be part of a solution that doesn't require reCAPTCHA. > If you lock people out after a certain number of failed login attempts, you allow an adversary to DOS your users by constantly trying to log in as them. That isn't how the pattern works. On next successful login you basically inform the user that they need to confirm it's them with an email token. It works well. ReCAPTCHA doesn't.