11-29-2005
I have updated my syslog.conf with the following auth.x entries (and cycled syslogd) :
auth.notice;auth.crit;auth.info /var/log/authlog
I see that login failure information is being captured, but the ID (or even a Generic ID) is NOT...
Nov 29 08:03:31 testBOX.com login: [ID 143248 auth.notice] Login failure on /dev/pts/2 from mybox.com
Nov 29 08:03:38 testBOX.com last message repeated 1 time
Nov 29 08:03:42 testBOX.com login: [ID 760094 auth.crit] REPEATED LOGIN FAILURES ON /dev/pts/2 FROM mybox.com
Nov 29 08:06:48 testBOX.com login: [ID 143248 auth.notice] Login failure on /dev/pts/2 from mybox.com
Nov 29 08:06:55 testBOX.com last message repeated 1 time
Nov 29 08:06:59 testBOX.com login: [ID 760094 auth.crit] REPEATED LOGIN FAILURES ON /dev/pts/2 FROM mybox.com
Nov 29 08:19:21 testBOX.com login: [ID 143248 auth.notice] Login failure on /dev/pts/2 from mybox.com
Nov 29 08:19:26 testBOX.com last message repeated 1 time
Nov 29 08:19:30 testBOX.com login: [ID 760094 auth.crit] REPEATED LOGIN FAILURES ON /dev/pts/2 FROM mybox.com
Also, does anyone know where I can get a list of valid facilities?
wondering what other options are out there...
thanks
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I notice in my Sun Solaris 8 sparc workstation, if I failed my login in the 5th time, I will be closed the connection from the host.
I want to make 3 times. That is, if user fails to login with 3 attempts, he will be closed the connection.
How to do it? Of course I am the admin of the... (2 Replies)
Discussion started by: champion
2 Replies
2. AIX
Hi. I would like to be able to deny IP address for too many failed login attemps (either from ssh, sftp, ftp, etc). The system I wish this to work on is an AIX 5.1 system. I'm new to AIX but I'm a linux user. There is a program for linux called fail2ban which reads from the log files and see if... (1 Reply)
Discussion started by: metzgerh
1 Replies
3. AIX
Does anyone have a good script / cron job that handles this?
I have looked in smit and see it is clearing this count with:
chsec -f /etc/security/lastlog -a "unsuccessful_login_count=0" -s '{userid}'
However when I looked around to find ways to automate this I have not found an easy... (0 Replies)
Discussion started by: Keith Johnson
0 Replies
4. Solaris
Hi,
I want to sent number of login attempts ,so that after that much attempts user account should be locked on solaris 10 (2 Replies)
Discussion started by: manoj.solaris
2 Replies
5. AIX
How can I see the number of invalid login attempts of a user?
Thanks, (9 Replies)
Discussion started by: agasamapetilon
9 Replies
6. Solaris
Hi Admins,
HOW to set unlimited login attempts for user in Solaris ?
And do I need to insatll any packages before doing this?
Thanks. (1 Reply)
Discussion started by: manalisharmabe
1 Replies
7. Cybersecurity
I'm stumped on an issue I'm having with RSA key based SSH logons.
I have 30 servers in a database cluster. They are all Red Hat Enterprise Linux Server release 6.4.
I want to be able to run a command on all of them from any one of them using SSH.
I generated private and public keys on... (1 Reply)
Discussion started by: derndingle
1 Replies
8. Solaris
Hi there,
In Solaris 8.
I have accidentally set the eeprom security-mode=command because I followed the CIS benchmark guideline. Initally, it was eeprom security-mode=none. I have tried to login with the correct password numerous time and it still say permission denied.
I have tried to login... (4 Replies)
Discussion started by: alvinoo
4 Replies
9. Cybersecurity
The purpose of this thread is for everyone to follow the same methodology so we can create a future table, for the benefit of all, that shows how many failed login attempts (hacking) per day per server (and per minute) are happening.
This is not a thread on writing scripts or creating... (10 Replies)
Discussion started by: Neo
10 Replies
LEARN ABOUT OSF1
syslog.auth
syslog.auth(4) Kernel Interfaces Manual syslog.auth(4)
NAME
syslog.auth - authorization file for accepting remote syslog messages
SYNOPSIS
# format: Each fully qualified host name on a separate line hostname.domain_name
DESCRIPTION
The /etc/syslog.auth file specifies which remote hosts are allowed to forward syslog messages to the local host. For the sake of security,
only messages coming from remote hosts listed in the local /etc/syslog.auth file will be logged by the syslogd daemon.
If the /etc/syslog.auth file does not exist, then messages coming from any host will be accepted.
Each remote host name should appear in a separate line in /etc/syslog.auth. A line started with the # character is considered as a comment
and is thus ignored.
A host name must be a complete domain name such as trout.zk3.dec.com. If a domain host name is given, it must either appear in the local
/etc/hosts file or be able to be resolved by the local name server (BIND).
Note that a host name can have at most as many characters as defined by the MAXHOSTNAMELEN constant in <sys/param.h>, although each line
in the /etc/syslog.auth file can have up to 512 characters.
The /etc/syslog.auth file must be owned by root and has a permission of 0600.
To invoke a new version of the /etc/syslog.auth file, run the following command (as the super user) to initialize the syslogd daemon: kill
-HUP `cat /var/run/syslog.pid`
EXAMPLES
The following example provides a typical authorization file: # format: Each fully qualified host name on a separate line
c3poid.rvo.dec.com r2d2id.ckt.dec.com
FILES
Location of the authorization file.
RELATED INFORMATION
Commands: syslogd(8), syslog(1)
System Administration delim off
syslog.auth(4)