Sponsored Content
Top Forums UNIX for Dummies Questions & Answers block user account after failed password Post 302433835 by pludi on Wednesday 30th of June 2010 04:34:47 PM
Old 06-30-2010
From the man page of pam_tally
Quote:
lock_time=n
Always deny for n seconds after failed attempt.

unlock_time=n
Allow access after n seconds after failed attempt. If this option is used the user will be locked out for the specified amount of time after he exceeded his maximum allowed attempts. Otherwise the account is locked until the lock is removed by a manual intervention of the system administrator.
In my interpretation (tho I'm not sure) this means that lock_time will block access for a certain time after each failed attempt, which would be useful to slow down a brute-force attack. unlock_time, however, sets the time until an account is automatically unlocked after the maximum number of tries.
This User Gave Thanks to pludi For This Post:
 

10 More Discussions You Might Find Interesting

1. Solaris

how can I change user name and password , of account ?

passwd only changes the password but i need to change the user name tnx (5 Replies)
Discussion started by: umen
5 Replies

2. UNIX for Dummies Questions & Answers

Change Account to not lock account if password expires

I have access to 15+ UNIX boxes at work, and I do not consistently log onto all of them over time. When I do try to access one I havent been on in awhile, my account is locked as the password has expired. I need to request to the UNIX SA's that the password expiration is 90 days and that if it... (1 Reply)
Discussion started by: stringzz
1 Replies

3. UNIX for Dummies Questions & Answers

Difference between : Locked User Account & Disabled User Accounts in Linux ?

Thanks AVKlinux (3 Replies)
Discussion started by: avklinux
3 Replies

4. Debian

password less login to root from a user account

hello friends, one user is created named "user1" I login as "user1" . Now when i do "su -" to be root user I have to give password for root . Is there any way through which we can skip giving the password to root. i.e. user1@work:~$ su - Password: xxxxxx work:~$ I don't want that... (1 Reply)
Discussion started by: pradeepreddy
1 Replies

5. Shell Programming and Scripting

Create new user account and password in shell script

I am trying to create a shell script that will: check if a specific user already exists if not, create a specific group and create the user in that group assign a password to that user, where the password is passed in as a parameter to the script The problem that I need help with is 3 on... (4 Replies)
Discussion started by: killuane
4 Replies

6. Solaris

Set Password Account to NP or NL

Hi Everyone, my name`s Sergio. I need your help please. I have a problem using Solaris 9. I create an account with the command line "useradd", with this I have no problem. My problem is I need set the created account to NP (No Password or Non Login). For example: cat /etc/shadow ... (2 Replies)
Discussion started by: roswell
2 Replies

7. Shell Programming and Scripting

Passing password when changing the user account

Hi All, I have one requirment.. I need to change my id to some sudo account in a server.. Actually our username/passwd will be stored in one gip file like below... $cat .a.gz #It's hidden file username passwd $ So I tried the below script to pass the password when i sudo to... (7 Replies)
Discussion started by: raghu.iv85
7 Replies

8. Shell Programming and Scripting

Need a condition to account for failed nslookups

I need some help creating a condition for looking up hosts. I have this master host file that has data in the following columns: FQDN primary IP secondary IP third IP I need the hostnames to feed into another script I use for provisioning users. The FQDN doesn't always work for... (2 Replies)
Discussion started by: MaindotC
2 Replies

9. Red Hat

Failed password for invalid user

Dear All , I have created a user named X and gave sudo permissions for it , So that it can access some commands as root. This particular user can login to the server using SSH login through putty any where with in the network. But there is some issue , when the same user is trying from... (4 Replies)
Discussion started by: jegaraman
4 Replies

10. Forum Support Area for Unregistered Users & Account Problems

Further to my query re: failed attempt to change email address on existing account

Neo Thanks for your reply to my original post, entitled "Problem changing the email address associated with my unix.com account". I am unable to reply to you in that thread, as I am unable to log-on to unix.com! From what you said about purging dormant accounts, it is likely that my account... (1 Reply)
Discussion started by: irb
1 Replies
prpwd(4)						     Kernel Interfaces Manual							  prpwd(4)

NAME
prpwd - protected password authentication database files used for trusted systems SYNOPSIS
DESCRIPTION
An authentication profile is maintained for each user on the system. A user profile is kept in a protected password database file that is accessible only to the System Administrator. The protected password database files contain among other things the encrypted password for the user account. On a trusted system, the passwords are hidden from normal users. The protected password database files do not obviate the need for the and the files. Users must be defined in the file in order to use the system. The protected password database file for a user contains the user name and user id to provide a correlation to the user's entry. These must match or the user account will be treated as invalid. Protected password database files are maintained in the hierarchy. This directory contains other directories each named with a single let- ter from the alphabet. User authentication profiles are stored in these directories based on the first letter of the user account name. This enables an efficient search operation to locate the file for a specific user name. For instance, the authentication profile for the account is located in the directory and can be accessed by opening the file Fields defined in a file are user specific values. These values override the system default values. Trusted programs check first for the existence of user specific parameters before using a system default value. A protected password database file contains keyword field identifiers and, depending on the field type, a value for that field (certain field types do not require an explicit value). The exact syntax for field specifications is described in authcap(4). Field specification is consistent for all system authentication databases. The keyword field identifiers supported by the protected password database file and their associated function are given in the following descriptions: This is the user name for the account which must match the name of the file and the user name from the corresponding entry. This is the user ID for the account which must match the user id field of the corresponding entry. This field contains the encrypted password for the account if the account has a password. This field contains the owner of the account. If this field exists and contains a value greater than zero (typically 1), and the boot authenticate flag is set in the system default file, then this user has authority to boot the system. If the boot authenticate flag is not set in the system default file then this field is not used. This field contains the audit ID for the user. This field contains the audit flag for the user. This field specifies the minimum password change time in seconds. If non-zero, the password cannot be changed until the specified number of seconds since the last successful password change have passed unless the person changing the password is authorized to override this constraint. This field specifies the maximum length for system-generated passwords. It should be less than the system-wide maximum value defined by the constant This field is a time_t value that specifies when the account password will expire. When a password expires, system authentication pro- grams will request that the password be changed when the user logs into the system. If the password lifetime expires before the password is changed, the account will be locked. This field is a time_t value that specifies the lifetime of a password. If this time is reached, the account will be locked and can only be unlocked by an authorized system administrator. This field is a time_t value that indicates the time of the last successful password change. This field should only be set by programs that can be used to change the account password. This field is a time_t value that indicates the time of the last unsuccessful password change. This field should only be set by programs that can be used to change the account password. This field is the time_t time in seconds that the account will be usable. After this time interval the user will no longer be allowed to login. This field is different from the field in that the field is the time from the last password change. is not affected by the changing of the password. This value, in seconds, is the maximum time allowed between logins. If the time between the last login and the current time exceeds this value, the account is locked and the user can no longer logon. This value, in seconds, is the time at which a warning will appear prior to the expiration of the user's password. This value is a flag that controls the ability of the user to pick a password for the account. This permits an account to be configured so that a user can not pick a password but instead has a pass- word generated by the system for the account. This flag field controls the ability of a user to generate a password for the account. The system is capable of generating passwords containing random letters, characters, or words. This flag field controls whether password triviality checks are performed on any user chosen passwords. Triviality checks performed include verifying that the password does not represent a login or group name, a palindrome, or a word recognized by the spell(1) program. This flag controls the ability of the user to choose a null password for the account. This field records the user id of the last person to change the account password if that user was not the same as the account's user. This is used to warn the user at login time if the account password has been changed possibly without the knowledge of the user. This field holds the random number the user must supply to login after the account is reset by the system administrator. This field is removed after a successful login. This flag field controls the ability of the user to generate random characters for a password. This flag field controls the ability of the user to generate random letters for a password. This field contains a comma separated list of time-of-day specification entries that controls when the user account can be used for login. This field is a time_t value that contains the system time of the last successful login to the account. This field is a time_t value that contains the system time of the last unsuccessful login to the account. This field is a character string that identifies the name of the terminal or remote host associated with the last successful login to the account. A remote host specification consists of the ASCII representation of the Internet address of the host. This field is con- verted into an Internet address and is converted to a hostname using gethostbyaddr(3). This field contains a count of the number of unsuccessful login attempts to the account. This field is reset when a successful login to the account occurs. This field is a character string that identifies the name of the terminal or remote host associated with the last unsuccessful login attempt to the account. This field specifies the maximum number of consecutive unsuccessful login attempts to the account that are permitted until the account is locked. This flag field is used to administratively lock an account. A user cannot login to a locked account. Notes The getprpwent(3) routines are used to parse the protected password database files into a structure that can used by programs. A flag in the structure indicates whether a particular field in the structure and hence the field is defined. System default values are also pro- vided in the structure. These values are derived from the field and can be used by programs in the absence of a user specific value. EXAMPLES
The following is an example of a typical protected password database file: perry:u_name=perry:u_id#101: :u_pwd=aZXtu1kmSpEzm: :u_minchg#0:u_succhg#653793862:u_unsucchg#622581606:u_nullpw: :u_suclog#671996425:u_suctty=tty1: :u_unsuclog#660768767:u_unsuctty=tty1: :u_maxtries#3:chkent: This protected password database file is for the user The user ID for is 101. This value must match the entry for this user. The account has a password and its encrypted form is specified by the field. The database file specifies a minimum password change time of 0, indicating the password can be changed at any time. Furthermore, the account is permitted to have a null password The account has a maximum consecutive unsuccessful login threshold of 3 attempts indicating that the account will be locked after three failed attempts The remaining fields provide account information such as the last successful and unsuccessful password change times as well as the last successful and unsuccessful login times and terminal names. WARNINGS
HP-UX 11i Version 3 is the last release to support trusted systems functionality. AUTHOR
was developed by HP. SEE ALSO
login(1), users(1), getprpwent(3), authcap(4), default(4). TO BE OBSOLETED prpwd(4)
All times are GMT -4. The time now is 03:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy