08-09-2014
I am not AIX fluent at all, but IBM always has something comparable to what other UNIX flavors have. Generally, there is always a system log and an su log (su usage) as well. Your sysadmin can look in those files to find the user (a user who tries to login and fails is the most likely candidate) that is locking the account with login failures. When an account is locked because of login fails, a message is usually written to a log.
The AIX guys can tell you exactly, but if your sysadmin does not know where to look (or if logfails monitoring is turned off) you have worse problems than a locked out account.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Every one
I disable the root account entering wrong password for many time
How can I enable the root account
I am using Tru64 Unix V4.0G
Thank you (2 Replies)
Discussion started by: Syed_45
2 Replies
2. AIX
I'am set the root account locked ON, using smitty, so I can't login or su with root user in my AIX system, some one can help me to unlock root account login ???,
sample :
:~>su
root's Password:
3004-301 Your account has been locked; please see the system administrator.
3004-501 Cannot su to... (1 Reply)
Discussion started by: Maker
1 Replies
3. Linux
Hi all,
I've been using linux/unix now only for a couple of months and was doing ok until about 30 minutes ago...
I needed to reboot into my windows 2000 partition, so, in a terminal I typed:
shutdown -r now
which duly rebooted the PC for me. On getting to the OS selection screen I... (5 Replies)
Discussion started by: alarmcall
5 Replies
4. HP-UX
I knew I had had seen this somewhere:Q: How can I re-enable my root account when I typed in my password wrong 3 times and the account got disabled?
A: When your HP-UX system is in the more secure "trusted system" mode, your account is automatically disabled after
you have entered your password... (0 Replies)
Discussion started by: Perderabo
0 Replies
5. AIX
we have a user name "Test1" that account is alwyas locked out. The user has been used to many servers to ftp a file from the main server. i already increase the MaxStartups to 99. And still after how many days account will locked. (3 Replies)
Discussion started by: invinzin21
3 Replies
6. Solaris
Hi,
I have enable Account lock for failed login attempts.
I have configured
1) /etc/security/policy.conf
2)/etc/default/login
To lock an account if it make multiple incorrect attempts to login to Solaris 10 server.
I can see the account gets locked in /etc/shadow.
I would like to... (1 Reply)
Discussion started by: menonk
1 Replies
7. Shell Programming and Scripting
Hi,
Can someone help me in running a cronjob everyday between 7 and 8 pm with the time interval of 5 minutes in between to repeat that script. The script is so small and I need that to run daily between this time. Please if possible provide me the syntax for this logic.
Thanks. (4 Replies)
Discussion started by: cya
4 Replies
8. UNIX for Dummies Questions & Answers
Hi
How do i list all locked account in my linux distributiion
I have tried
passwd -S -a
but it seems to not working .
My distribution details.
# lsb_release -a
LSB Version: :core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch
Distributor ID: OracleVMserver... (3 Replies)
Discussion started by: pinga123
3 Replies
9. UNIX for Dummies Questions & Answers
Hi,
When I am trying to do ssh to a server it shows below error.
Key setup is all good and it used to work well few days back. Now suddenly I am getting this error.
ssh -i <private_key> <id>@<hostname>
Received disconnect from <hostname> Account is locked or login administratively... (1 Reply)
Discussion started by: mahish20
1 Replies
10. Solaris
I am facing strange problem where after three failed login attempt user password must be locked. Actually what is happening, when I take the putty session of the server & enter user name on the prompt at the login prompt & then press enter to enter the password at this time when I checked the... (10 Replies)
Discussion started by: sb200
10 Replies
LEARN ABOUT CENTOS
pam_lastlog
PAM_LASTLOG(8) Linux-PAM Manual PAM_LASTLOG(8)
NAME
pam_lastlog - PAM module to display date of last login and perform inactive account lock out
SYNOPSIS
pam_lastlog.so [debug] [silent] [never] [nodate] [nohost] [noterm] [nowtmp] [noupdate] [showfailed] [inactive=<days>]
DESCRIPTION
pam_lastlog is a PAM module to display a line of information about the last login of the user. In addition, the module maintains the
/var/log/lastlog file.
Some applications may perform this function themselves. In such cases, this module is not necessary.
If the module is called in the auth or account phase, the accounts that were not used recently enough will be disallowed to log in. The
check is not performed for the root account so the root is never locked out.
OPTIONS
debug
Print debug information.
silent
Don't inform the user about any previous login, just update the /var/log/lastlog file.
never
If the /var/log/lastlog file does not contain any old entries for the user, indicate that the user has never previously logged in with
a welcome message.
nodate
Don't display the date of the last login.
noterm
Don't display the terminal name on which the last login was attempted.
nohost
Don't indicate from which host the last login was attempted.
nowtmp
Don't update the wtmp entry.
noupdate
Don't update any file.
showfailed
Display number of failed login attempts and the date of the last failed attempt from btmp. The date is not displayed when nodate is
specified.
inactive=<days>
This option is specific for the auth or account phase. It specifies the number of days after the last login of the user when the user
will be locked out by the module. The default value is 90.
MODULE TYPES PROVIDED
The auth and account module type allows to lock out users which did not login recently enough. The session module type is provided for
displaying the information about the last login and/or updating the lastlog and wtmp files.
RETURN VALUES
PAM_SUCCESS
Everything was successful.
PAM_SERVICE_ERR
Internal service module error.
PAM_USER_UNKNOWN
User not known.
PAM_AUTH_ERR
User locked out in the auth or account phase due to inactivity.
PAM_IGNORE
There was an error during reading the lastlog file in the auth or account phase and thus inactivity of the user cannot be determined.
EXAMPLES
Add the following line to /etc/pam.d/login to display the last login time of an user:
session required pam_lastlog.so nowtmp
To reject the user if he did not login during the previous 50 days the following line can be used:
auth required pam_lastlog.so inactive=50
FILES
/var/log/lastlog
Lastlog logging file
SEE ALSO
pam.conf(5), pam.d(5), pam(8)
AUTHOR
pam_lastlog was written by Andrew G. Morgan <morgan@kernel.org>.
Inactive account lock out added by Toma Mraz <tm@t8m.info>.
Linux-PAM Manual 09/19/2013 PAM_LASTLOG(8)