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
SHADOW(5) File Formats and Conversions SHADOW(5)
NAME
shadow - shadowed password file
DESCRIPTION
shadow is a file which contains the password information for the system's accounts and optional aging information.
This file must not be readable by regular users if password security is to be maintained.
Each line of this file contains 9 fields, separated by colons (":"), in the following order:
login name
It must be a valid account name, which exist on the system.
encrypted password
Refer to crypt(3) for details on how this string is interpreted.
If the password field contains some string that is not a valid result of crypt(3), for instance ! or *, the user will not be able to
use a unix password to log in (but the user may log in the system by other means).
This field may be empty, in which case no passwords are required to authenticate as the specified login name. However, some
applications which read the /etc/shadow file may decide not to permit any access at all if the password field is empty.
A password field which starts with an exclamation mark means that the password is locked. The remaining characters on the line
represent the password field before the password was locked.
date of last password change
The date of the last password change, expressed as the number of days since Jan 1, 1970.
The value 0 has a special meaning, which is that the user should change her password the next time she will log in the system.
An empty field means that password aging features are disabled.
minimum password age
The minimum password age is the number of days the user will have to wait before she will be allowed to change her password again.
An empty field and value 0 mean that there are no minimum password age.
maximum password age
The maximum password age is the number of days after which the user will have to change her password.
After this number of days is elapsed, the password may still be valid. The user should be asked to change her password the next time
she will log in.
An empty field means that there are no maximum password age, no password warning period, and no password inactivity period (see below).
If the maximum password age is lower than the minimum password age, the user cannot change her password.
password warning period
The number of days before a password is going to expire (see the maximum password age above) during which the user should be warned.
An empty field and value 0 mean that there are no password warning period.
password inactivity period
The number of days after a password has expired (see the maximum password age above) during which the password should still be accepted
(and the user should update her password during the next login).
After expiration of the password and this expiration period is elapsed, no login is possible using the current user's password. The
user should contact her administrator.
An empty field means that there are no enforcement of an inactivity period.
account expiration date
The date of expiration of the account, expressed as the number of days since Jan 1, 1970.
Note that an account expiration differs from a password expiration. In case of an account expiration, the user shall not be allowed to
login. In case of a password expiration, the user is not allowed to login using her password.
An empty field means that the account will never expire.
The value 0 should not be used as it is interpreted as either an account with no expiration, or as an expiration on Jan 1, 1970.
reserved field
This field is reserved for future use.
FILES
/etc/passwd
User account information.
/etc/shadow
Secure user account information.
/etc/shadow-
Backup file for /etc/shadow.
Note that this file is used by the tools of the shadow toolsuite, but not by all user and password management tools.
SEE ALSO
chage(1), login(1), passwd(1), passwd(5), pwck(8), pwconv(8), pwunconv(8), su(1), sulogin(8).
shadow-utils 4.5 01/25/2018 SHADOW(5)