07-31-2014
That's a cool thing, but if the users come via LDAP you will have to draw a list of user names at least maybe once a day to update that dict file.
10 More Discussions You Might Find Interesting
1. UNIX and Linux Applications
Hi all of you..............
I am using openldap on ubuntu server . i want to apply password policy for user's to set password length , expire date , ......etc.
can anybody guide me to configure this. (1 Reply)
Discussion started by: jagnikam
1 Replies
2. Solaris
Hi Solaris's expert
I need to change user password on Solaris10 2 servers.
With the same password I can change it just only one.
Try to check everything but not found difference??
password pattern: abcdeFgh9Jk
server1 check all characters but server2 check only first 8 characters.Why??... (10 Replies)
Discussion started by: arm_naja
10 Replies
3. Red Hat
Today i was going through some of security guides written on linux .
Under shadow file security following points were mentioned.
1)The encrypted password stored under /etc/shadow file should have more than 14-25 characters.
2)Usernames in shadow file must satisfy to all the same rules as... (14 Replies)
Discussion started by: pinga123
14 Replies
4. Red Hat
Hi,
I am running NIS server on redhat linux 5 and I want to implement password restrictions for the yppasswd, how can I do it.Please help me.
I can implement password restriction for passwd by configuring /etc/pam.d/system-auth and setting crack_lib.so but I don't know how to implent the same... (3 Replies)
Discussion started by: ktrimu
3 Replies
5. Solaris
hi folk,
i try to setup a new password policy for our solaris box user, below are the /etc/default/passwd/, but then when i tried to create a user, it didn't ask for numeric character, and the new password also didn't ask for special characters.
# useradd testing
# passwd testing
New... (7 Replies)
Discussion started by: dehetoxic
7 Replies
6. Ubuntu
Hi linux expert,
i would like to create a script for listing all user with there password policy. It should be in the following format:
Last password change : Sep 19, 2011
Password expires : never
Password inactive : never
Account... (2 Replies)
Discussion started by: yprudent
2 Replies
7. Red Hat
Hi Experts,
i would like to know the description of the following:
Minimum: 0
Maximum: 90
Warning: 7
Inactive: -1
Last Change: Never
Password Expires: Never
Password Inactive: Never
Account Expires: Never
Does this means that... (2 Replies)
Discussion started by: yprudent
2 Replies
8. Solaris
Hello All,
I have Sun DSEE7 (11g) on Solaris 10.
I have run idsconfig and initialized ldap client with profile created using idsconfig.
My ldap authentication works. Here is my pam.conf
# Authentication management
#
# login service (explicit because of pam_dial_auth)
#
login ... (3 Replies)
Discussion started by: pandu345
3 Replies
9. Ubuntu
Hello Team,
I am using Lubuntu & have DRBL remote boot setup with open Ldap authentication. Currently there is no password expire policy. I want to set Password Policy so that user's password will expire after a month & they will get prompt to change their password.
Using PAM we can do it,... (1 Reply)
Discussion started by: paragnehete
1 Replies
10. Red Hat
Hi,
I am unable to enforce password complexity policy for root user. (other users are working) on RHEL 6.2. Anything wrong with system-auth parameters? PLease help..
vi /etc/pam.d/system-auth
#%PAM-1.0
# This file is auto-generated.
# User changes will be destroyed the next time... (1 Reply)
Discussion started by: suresh3566
1 Replies
authck(1M) authck(1M)
NAME
authck - check internal consistency of Authentication database
SYNOPSIS
DESCRIPTION
The command only works for systems that have been converted to trusted mode.
checks both the overall structure and internal field consistency of all components of the Authentication database. It reports all problems
it finds. Only users who have the superuser capability can run this command. When is used with the option, is run with the option auto-
matically.
Options
recognizes the following options and tests:
Check the Protected Password database.
The Protected Password database and are checked for completeness such that neither contains entries not in the other. The
cross references between the Protected Password database and are checked to make sure that they agree. If a user does NOT
exist in but exists in the Protected Password database, then all inconsistencies are reported. Fields in the Protected
Password database are then checked for reasonable values. For example, all time stamps of past events are checked to make
sure that they have times less than the times returned by time(2).
Fields in the Terminal Control database are checked for reasonable values.
All time stamps of past events are checked to make sure they have times less than those returned by time(2).
Shorthand equivalent of using the
and options together in a single command.
Provide running diagnostics as the program proceeds.
Produce warnings when unusual conditions are encountered that might not cause program errors in login, password and su pro-
grams.
WARNINGS
HP-UX 11i Version 3 is the last release to support trusted systems functionality.
FILES
System password file
Protected Password database
Terminal Control database
System Defaults database
AUTHOR
was developed by HP.
SEE ALSO
getprpwent(3), getprtcent(3), getprdfent(3), authcap(4).
TO BE OBSOLETED authck(1M)