Sponsored Content
Full Discussion: Account lockout policy
Operating Systems Linux Red Hat Account lockout policy Post 302423504 by maverick_here on Friday 21st of May 2010 07:50:18 AM
Old 05-21-2010
Account lockout policy

Hi all;

I m using Red Hat Enterprise Linux Server release 5.1 (Tikanga) and I'm trying to setup password lockout policy so that a user account locks out after 3 failed attempts.

Here are the entires of my /etc/pam.d/system-auth

Code:
#%PAM-1.0
# This file is auto-generated.
# User changes will be destroyed the next time authconfig is run.
auth        required      pam_env.so
auth        required      pam_tally.so onerr=fail no_magic_root
auth        sufficient    pam_unix.so nullok try_first_pass
auth        requisite     pam_succeed_if.so uid >= 500 quiet
auth        required      pam_deny.so

account     required      pam_unix.so
account     required      pam_tally.so deny=3 no_magic_root reset
account     sufficient    pam_succeed_if.so uid < 500 quiet
account     required      pam_permit.so

password    requisite     pam_cracklib.so try_first_pass retry=3
password    sufficient    pam_unix.so md5 shadow nullok try_first_pass use_authtok
password    required      pam_deny.so

session     optional      pam_keyinit.so revoke
session     required      pam_limits.so
session     [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
session     required      pam_unix.so

I have a /var/log/faillog.

How ever when i test it by failing to authenticate a user it is not locking the user account.Is there something that I'm missing.Please advise.

Regards,
Syed

Moderator's Comments:
Mod Comment Added code tags

Last edited by Scott; 05-21-2010 at 09:18 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Lockout Users

I am using AIx 4.3.3 and was wondering what the command was to keep users from logging in. I want to be able to do maintenance and keep the users out. Can anyone help? (7 Replies)
Discussion started by: cgillett
7 Replies

2. UNIX for Dummies Questions & Answers

root lockout

Hi, I am extremely new to UNIX and was recently promoted to administer the system for a small company. Anyhow, the time came for passwords to change, and I made the huge mistake of entering in the command (as root) passwd -l After logging out (oblivious to what would happen next), the root... (4 Replies)
Discussion started by: newbieadmin
4 Replies

3. AIX

user lockout...

Hi, We are using 4.3.3.0 and I would like to make a global change to the "number of failed logins before user account is locked" Any ideas, other than using SMIT one user at a time.... ??? Thanks... Craig. (2 Replies)
Discussion started by: stumpy
2 Replies

4. AIX

lockout su for 1 user

I want to know if there is any easy way of stopping 1 user from using su? perferabily any su but I can make do with not allow him to su to root but allow other user to su to root. (3 Replies)
Discussion started by: daveisme
3 Replies

5. UNIX and Linux Applications

Account lockout using Openldap

What is the best way to implement account lockout in openldap? I have an openldap server with Ubuntu desktop client connecting to it for authentication. I want he accounts to locked out after say 5 failed authentication attempts I have enabled ppolicy layout in slapd.conf. overlay ppolicy... (0 Replies)
Discussion started by: nitin09
0 Replies

6. Red Hat

Account Lockout on Redhat

On a redhat linux 4 server, how to find if there is an account lockout duration is set. Is it configured under pam or /etc/shadow? what entries I need to find out? Is it pam_time.so module? I desperately need an answer because on one of the servers, no one was able to login through any account... (4 Replies)
Discussion started by: Tirmazi
4 Replies

7. Linux

User Account Policy

Hi, i have the following config in the system-auth files auth required /lib/security/$ISA/pam_env.so auth sufficient /lib/security/$ISA/pam_unix.so likeauth nullok auth required /lib/security/$ISA/pam_deny.so account required ... (2 Replies)
Discussion started by: yprudent
2 Replies

8. Red Hat

Account lockout

having account lockout issues with an RHEL 5 server. My users are getting locked out for 10 minutes after one failed login attempt even though /etc/pam.d/sshd is configured for 5 failed attempts: auth include system-auth auth required pam_tally2.so deny=5 onerr=fail... (1 Reply)
Discussion started by: nerdalert
1 Replies

9. Solaris

Secman lockout

Greetings, I work with a Solaris Sun Server V240 system (GCCS) and have run into a problem where I can't seem to unlock my SECMAN account at the NON-GLOBAL level. I have access to all global accounts to include sysadmin and secman. I have access to the non-global sysadmin account and root... (4 Replies)
Discussion started by: TLAMGUY
4 Replies

10. Red Hat

RHEL4.8 no notification on PAM lockout

Good day. I have setup hardening the password (test system so far) prior to doing any work on production. Here is what I have set. Snippet from /etc/pam.d/system-auth auth required /lib/security/$ISA/pam_env.so auth required /lib/security/$ISA/pam_tally.so... (3 Replies)
Discussion started by: smurphy_it
3 Replies
RHNREG_KS(8)							   Red Hat, Inc.						      RHNREG_KS(8)

NAME
rhnreg_ks - A program for non interactively registering systems to Spacewalk Server, Red Hat Satellite or Red Hat Network Classic. SYNOPSIS
rhnreg_ks [options] DESCRIPTION
rhnreg_ks is a utility for registering a system with the "Spacewalk Server", "Red Hat Satellite" or "Red Hat Network Classic". It is designed to be used in a non-interactive environment (a kickstart style install, for example). All the information can be specified on the command line or stdin. OPTIONS
--profilename Specify the profile name that should be used as an identifier for the system in Spacewalk Server, Red Hat Satellite or Red Hat Net- work Classic --username The username to register the system with under Spacewalk Server, Red Hat Satellite or Red Hat Network Classic. This can be an exist- ing Spacewalk, Red Hat Satellite or Red Hat Network Classic username, or a new username. --password The password associated with the username specified with the --username option. This is an unencrypted password. --activationkey Specify/use a serial number to associate with the system. This is optional, but activation keys can really simplify the registration process. Learn more about activation keys in the online RHN documentation. --contactinfo This option has been deprecated. Please login to the server web user interface and update your contactinfo. --nohardware Do not probe or upload any hardware information. --nopackages Do not profile or upload any package information. --novirtinfo Do not profile or upload any virtualization information. --norhnsd Do not start rhnsd after completion. --force Register the system even if it has already been registered. --version Show the version of rhnreg_ks. --proxy Specify a HTTP proxy to use. --proxyUser Specify a username to use with an authenticated HTTP proxy. --proxyPassword Specify a password to use with an authenticated HTTP proxy. --sslCACert Specify a path to a SSL CA certificate to use. --serverUrl Specify a URL to as the server. -h, --help Show a help message and exit. FILES
/etc/sysconfig/rhn/systemid The digital server ID for this machine if the system has been registered onto "Spacewalk Server", "Red Hat Satellite" or "Red Hat Network Classic". This file does not exist otherwise. /etc/sysconfig/rhn/up2date The common configuration file used by RHN client programs. EXAMPLES
Register a new system to Spacewalk / Red Hat Satellite / Red Hat Network Classic: rhnreg_ks --profilename "example_profile_name" --username "someexampleuser" --password "foobar" SEE ALSO
rhn_check(8), rhn_register(8), rhnsd(8), rhn-profile-sync(8), rhnplugin(8), up2date(5). AUTHORS
See the AUTHORS file included with this software. This manual page was written by Adrian Likins <alikins@redhat.com> and James Bowes <jbowes@redhat.com> BUGS
Report bugs to <http://bugzilla.redhat.com>. COPYRIGHT
Copyright (C) 1999-2011 Red Hat, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU- LAR PURPOSE. Linux 2011 February 4 RHNREG_KS(8)
All times are GMT -4. The time now is 11:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy