MLUG: Re: [MLUG] Lax security practices?
Re: [MLUG] Lax security practices?
Email address obfuscation in effect -- please click here to turn it off.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
It is located at

/var/log/auth.log on my system.

You can also grab fail2ban from sourceforge at:
http://fail2ban.sourceforge.net/

Debian-administration.org also has an install guide for a python script that acts much like fail2ban. On debian, fail2ban is MUCH better/easier to install, but the python script should work with a little tweaking on any distro with python 2.3 or better.

http://www.debian-administration.org/articles/342

Josh.

Phillip Kelchen wrote:
I see a /var/log/warn in there that needs root to be able to cat it. It did 
give me a warning the two times I tried to login as root, but it was mostly 
full of warnings about not being able to find CPUs 2-127 (apparently the SMP 
kernel supports up to 128 CPUs) and tainted kernel modules. But I don't think 
that is what you were talking about. So I guess I will just have to keep 
looking around.

Phillip

On Tuesday 21 March 2006 22:37, Daniel Nowlin wrote:
  
It should be in your /var/log directory.  It may not be called auth.log
but you should have something like it.  SSHBlackList is not distro
specific so it should work with SUSE.  You will just have to do a little
setup in the program for your distro.

Dan
    

_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members
  
_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members