Re: OpenSSH keyboard-interactive authentication brute force vulnerability (MaxAuthTries bypass)

[Dirk-Willem van Gulik <dirkx () webweaving org>]

> On 18 Jul 2015, at 23:23, Reed Loden <reed () reedloden com> wrote:
>
> On Friday, July 17, 2015, <devel () roosoft ltd uk> wrote:
>
> > Do you know if this is still affected if you have fail2ban in place.
> > Fail2ban uses the auth logs to monitor failed password attempts. I
> > assume that the auth log is still updated even if x number of attempts
> > is allowed. Thanks
>
>
>
> http://www.reddit.com/r/netsec/comments/3dnzcq/openssh_keyboardinteractive_authentication_brute/ct726ni
> goes over this question pretty well, so as not to rehash everything.

Arguably the question then should be to have a MaxChallengeTries as an analog of MaxAuthTries - and perhaps by default
set MaxChallengeTries to the same (sane) value of MaxAuthTries.

Dw.

_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: http://seclists.org/fulldisclosure/