github
/
fail2ban
mirror of https://github.com/fail2ban/fail2ban
1
0
Fork 0
Code Issues Releases Wiki Activity

adjusted

debian-releases/etch
Yaroslav Halchenko 2006-03-03 21:14:34 +00:00
parent f8eaf92733
commit 046f219eaf
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
debian/README.Debian vendored
View File

@ -74,6 +74,8 @@ happening with firestarter), errors get reported during the exit of
fail2ban, but they are "safe" and can be ignored. fail2ban, but they are "safe" and can be ignored.
** SSHD Configuration Specific Problems
* Ban "Not allowed" attempts: * Ban "Not allowed" attempts:
Make sure that you have Make sure that you have
@ -85,6 +87,16 @@ Details from the bug report #350980 [2]
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=350980 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=350980
* Not caught attempts to login as root
On the boxes running older versions of openssh (e.g. sarge
distribution) in the case when PermitRootLogin is set to something
else than "yes" and iff AllowUsers is active, failed root logins do
not confirm to the standard logging message -- they omit the source
IP, thus allowing attack to persist since such messages are not caught
by fail2ban.
* Bantime: * Bantime:
An IP is banned for "bantime" not since the last failed login attempt An IP is banned for "bantime" not since the last failed login attempt