Sponsored Content
Operating Systems Solaris User account management Sol10 Post 302251985 by gwhelan on Tuesday 28th of October 2008 01:33:44 PM
Old 10-28-2008
Hi FloridaBSD.

I'm actually looking for the security attributes for passwords such as password length, must have uppercase/lowercase letters etc?

Is all the settings just held in the /etc/default/passwd file?

I'm also looking to get information on when the user accounts where created. Thanks.
 

9 More Discussions You Might Find Interesting

1. Cybersecurity

HP-UX user management

Hello All, Does anyone know of any good utilities for user management/password management for HP-UX? I have 32 switchs (telephone) running HP-UX 10x and managing the users on them is becoming quite time consuming... Thanks Brian (1 Reply)
Discussion started by: breigner
1 Replies

2. AIX

User Management

Can someone suggest me any means of having a controlled way to user access ... basically we have a varied environment of people(users) logging in to AIX boxes ... either via 1) telnet ... 2) application 3) databse (SQL's) what we need to do is formalise this .. can someone help me with this ... (2 Replies)
Discussion started by: rajesh_149
2 Replies

3. What is on Your Mind?

Root User Management

I am currently executing a Unix audit & would like some guidance on best practice for the management of root user access. The organisation is small, with an IT team of approx 25. (6 Replies)
Discussion started by: conaloregan
6 Replies

4. Solaris

Centralised Account Management

Hi all. be gentle, its my first time :-) I seem to have had this isse dumped on me and could do with help/advice. We have several Solaris10 servers, authentication is done per server using the usual useradd and the passwd/group/shadow files. we're now at a point where we need some way of... (4 Replies)
Discussion started by: boneyard
4 Replies

5. 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

6. Solaris

changing user password as root on LDAP client SOl10/u7

I'm fairly inexperienced with LDAP and DSEE so to build my skills I installed directory server in the global zone of my Sol 10/u7 machine and created a zone to use as a client. For some reason when I try to change a users password as root (in the client zone) with passwd -r ldap I am prompted for... (1 Reply)
Discussion started by: ilikecows
1 Replies

7. Linux

User Management in linux

Hi All, I have to learn all the user management commend like adduser,useradd,chggrp... etc I would like to know the syntax or example. Please give me document or link. Thanks, Mani (1 Reply)
Discussion started by: Mani_apr08
1 Replies

8. AIX

Help with user management

Hi When i search for a user it shows that the user doesn't exist # lsuser x090817 3004-687 User "x090817" does not exist. But under /var/spool/mail/ the file named x090817 still exists. 4700 1 -rw-rw---- 1 2090817 mail 603 Apr 12 2010 /var/spool/mail/x090817... (1 Reply)
Discussion started by: aixaixaixaix
1 Replies

9. HP-UX

User account

I need to check actual date a user was disabled on my HP-UX server. Audit is claiming the user account was active during the last audit exercise. (7 Replies)
Discussion started by: cyriac_N
7 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)
All times are GMT -4. The time now is 09:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy