01-07-2009
The lastlog file in /etc/security contains that information. You should be able to view it if you have root access and you could also write a script to search it. Good Luck.
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. Solaris
I am wondering if solaris captures id's associated w/invalid login attempts?
when I try to login as "test1" several (3-5) times, I do not find any userID info under "/var/adm" files:
utmpx
wtmpx
messages
lastlog
Is there another location/log I should be checking?
Is it necessary for... (6 Replies)
Discussion started by: mr_manny
6 Replies
3. 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
4. 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
5. 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
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
ttys(4) Kernel Interfaces Manual ttys(4)
NAME
ttys - terminal control database file for trusted systems
SYNOPSIS
DESCRIPTION
The system supports a single terminal control database containing entries for each local terminal that can log into the system. Authentica-
tion programs use information contained in the terminal control database to determine if login from the terminal is permitted. Additional
fields are maintained for informational purposes.
The format of the terminal control database file is identical to other system authentication database files. For more information on the
file format, see authcap(4). The file consists of keyword field identifiers and values for those fields. The keyword identifiers supported
and their use include:
This field defines the terminal device name for the entry. The terminal device
is expected to be contained in the directory, therefore this prefix should not be specified. If the terminal entry
describes the device, the field should contain
This field records the user id of the last user to successfully login using
the terminal device.
This field records the last successful login time to the terminal device.
This field records the last unsuccessful login time to the terminal device.
This field records the number of consecutive unsuccessful login attempts to
the terminal device.
This field specifies the maximum number of consecutive unsuccessful login
attempts permitted using the terminal before the terminal is locked. Once the terminal is locked, it must be unlocked by
an authorized administrator.
This field specifies the login timeout value (sec).
This field specifies the delay between login tries (sec).
This flag field indicates whether the terminal device has been administratively
locked or not. This field is manipulated by authorized administrators only.
EXAMPLES
The following is an example of a terminal control database entry:
This entry is for the system console device, The most recent successful login session was for the user The entry records the system time
for the current successful login and the time of the most recent unsuccessful login attempt.
WARNINGS
Remote terminals (ptys) should not be added to the or databases. Device name formats treated as ptys by login are:
where x is a letter, and y is a hex number
where x is a letter, and y is a hex number
HP-UX 11i Version 3 is the last release to support
trusted systems functionality.
AUTHOR
was developed by HP.
FILES
Terminal control database file
SEE ALSO
login(1), getprtcent(3), devassign(4), authcap(4), default(4).
TO BE OBSOLETED ttys(4)