9 More Discussions You Might Find Interesting
1. Red Hat
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
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
3. Red Hat
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
4. Red Hat
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
5. UNIX and Linux Applications
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
6. Red Hat
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
# This file is auto-generated.
# User changes... (1 Reply)
Discussion started by: maverick_here
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
We are using 184.108.40.206 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
9. UNIX for Dummies Questions & Answers
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)
After logging out (oblivious to what would happen next), the root... (4 Replies)
Discussion started by: newbieadmin
lpusers(1M) System Administration Commands lpusers(1M)
lpusers - set printing queue priorities
lpusers -d priority-level
lpusers -q priority-level -u login-ID-list
lpusers -u login-ID-list
lpusers -q priority-level
The lpusers command sets limits to the queue priority level that can be assigned to jobs submitted by users of the LP print service.
The first form of the command (with -d) sets the system-wide priority default to priority-level, where priority-level is a value of 0 to
39, with 0 being the highest priority. If a user does not specify a priority level with a print request (see lp(1)), the default priority
level is used. Initially, the default priority level is 20.
The second form of the command (with -q and -u) sets the default highest priority-level (0-39) that the users in login-ID-list can request
when submitting a print request. The login-ID-list argument may include any or all of the following constructs:
login-ID A user on any system
system_name!login-ID A user on the system system_name
system_name!all All users on system system_name
all!login-ID A user on all systems
all All users on all systems
Users that have been given a limit cannot submit a print request with a higher priority level than the one assigned, nor can they change a
request that has already been submitted to have a higher priority. Any print requests submitted with priority levels higher than allowed
will be given the highest priority allowed.
The third form of the command (with -u) removes any explicit priority level for the specified users.
The fourth form of the command (with -q) sets the default highest priority level for all users not explicitly covered by the use of the
second form of this command.
The last form of the command (with -l) lists the default priority level and the priority limits assigned to users.
The following options are supported:
Set the system-wide priority default to priority-level.
List the default priority level and the priority limits assigned to users.
Set the default highest priority level for all users not explicitly covered.
-q priority-level -u login-ID-list
Set the default highest priority-level that the users in login-ID-list can request when submitting a print request.
Remove any explicit priority level for the specified users.
The following exit values are returned:
0 Successful completion.
non-zero An error occurred.
See attributes(5) for descriptions of the following attributes:
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|Availability |SUNWpsu |
SunOS 5.10 19 Aug 1996 lpusers(1M)