lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <1C77EA92-5D2D-4C0E-942F-645A9EC3889B@webweaving.org> Date: Mon, 20 Jul 2015 10:24:08 +0200 From: Dirk-Willem van Gulik <dirkx@...weaving.org> To: Reed Loden <reed@...dloden.com> Cc: "fulldisclosure@...lists.org" <fulldisclosure@...lists.org> Subject: Re: [FD] OpenSSH keyboard-interactive authentication brute force vulnerability (MaxAuthTries bypass) > On 18 Jul 2015, at 23:23, Reed Loden <reed@...dloden.com> wrote: > > On Friday, July 17, 2015, <devel@...soft.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/
Powered by blists - more mailing lists