Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Clarification on /etc/passwd file entry Post 302138006 by Yogesh Sawant on Friday 28th of September 2007 07:23:00 AM
Old 09-28-2007
From the AIX documentation:
Code:
If a user ID has a password, then the password field will have an ! (exclamation point). If the user ID does not have a password, then the password field will have an * (asterisk). The encrypted passwords are stored in the /etc/security/passwd file.

 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Creating an entry for /etc/passwd

given an input file containing fields seperated by "," how do I retrieve information of these fields, do some work on them, then create a new input to the etc/passwd file? someone told me to look at the "sed" command but I still cant seem to get over this problem. I want to work on the data so... (8 Replies)
Discussion started by: sleepster
8 Replies

2. Programming

Whant to write an entry in /etc/passwd (putpwent)

Hi i try to use the function putpwent to write a simple entry in "/etc/passwd" putpwnet returns 0 as it works but notething writes to /etc/passwd. What have i missed? My os -------- root@nighter-laptop:/home/nighter/labb# uname -a Linux nighter-laptop 2.6.22-14-generic #1 SMP Sun Oct 14... (5 Replies)
Discussion started by: nighter
5 Replies

3. Linux

Cron ORPHAN (no passwd entry)

I am using the standard vixie-cron am seeing the following my logs : crond: (username) ORPHAN (no passwd entry) Ordinarily this is a simple matter, there is no corresponding user, but I am using central authentication and the username does exist and is usable via the standard nsswitch mechanism, so... (2 Replies)
Discussion started by: humbletech99
2 Replies

4. UNIX for Advanced & Expert Users

No entry in /etc/passwd

I could not find an entry for my linux user account in /etc/passwd file. I can remember some time back one of my SA showed the entry line using some other command. Can someone please help me on this to view the details of my linux user account? (3 Replies)
Discussion started by: apsprabhu
3 Replies

5. Solaris

passwd cmd reenables passwd aging in shadow entry

Hi Folks, I have Solaris 10, latest release. We have passwd aging set in /etc/defalut/passwd. I have an account that passwd should never expire. Acheived by emptying associated users shadow file entries for passwd aging. When I reset the users passwd using passwd command, it re enables... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

6. AIX

When did AIX start using /etc/security/passwd instead of /etc/passwd to store encrypted passwords?

Does anyone know when AIX started using /etc/security/passwd instead of /etc/passwd to store encrypted passwords? (1 Reply)
Discussion started by: Anne Neville
1 Replies

7. HP-UX

Sudo entry required to set permission similar to ROOT without using password (PASSWD) change optio

Hi All I had installed sudo in HP UX 11.3 and it is working fine but not able to make entry required to set permission similar to ROOT without using password (PASSWD) change option for define user in /etc/sudoers file Please help if some know the syntex? :confused::wall: (2 Replies)
Discussion started by: deviltech
2 Replies

8. UNIX for Advanced & Expert Users

Big problem: shell entry in /etc/passwd corrupted for user root

did a big mistake, changing root entry of /etc/passwd to root:x:0:0:root:/root:/usr/bin/tmux split-window -v \; attach as expected, now I can't login as root anymore. sudo ed /etc/passwd etc. doesn't work. Any idea? Use code tags to increase readability and follow the rules. (4 Replies)
Discussion started by: dodona
4 Replies
PASSWD(5)							File Formats Manual							 PASSWD(5)

NAME
passwd, group, shadow - user and group databases, shadow passwords SYNOPSIS
/etc/passwd /etc/group /etc/shadow DESCRIPTION
/etc/passwd lists all the users of the system, and /etc/group lists all the groups the users may belong to. Both files also contain encrypted passwords, numeric ID's etc. Encrypted passwords may be hidden in the file /etc/shadow if extra protection is warranted. Each file is an text file containing one line per user or group. The data fields on a line are separated by colons. Each line in the password file has the following form: name:passwd:uid:gid:gecos:dir:shell The name field is the login name of a user, it is up to 8 letters or numbers long starting with a letter. The login name must be unique. The password field is either empty (no password), a 13 character encrypted password as returned by crypt(3), or a login name preceded by two number signs (#) to index the shadow password file. Anything else (usually *) is invalid. The uid and gid fields are two numbers indicating the users user-id and group-id. These id's do not have to be unique, there may be more than one name with the same id's. The gecos field can be set by the user. It is expected to be a comma separated list of personal data where the first item is the full name of the user. The dir field is the path name of the users home directory. Lastly the shell field is the path name of the users login shell, it may be empty to indicate /bin/sh. A Minix specific extension allows the shell field to contain extra space separated arguments for the shell. Lines in the group file consist of four fields: name:passwd:gid:mem The name field is the name of the group, same restrictions as a login name. The passwd field may be used to let users change groups. The gid field is a number telling the group-id. The group-id is unique for a group. The mem field is a comma separated list of login names that are special members of the group. If a system supports supplementary group id's then a user's set of supplementary group id's is set to all the groups they are a member of. If a system allows one to change groups then one can change to a group one is a member of without using the group's password. The shadow password file has precisely the same form as the password file, except that only the name or passwd fields are used as yet. The other fields are zero or empty. A password in the password file may have the form ##user to indicate the entry user in the shadow password file. The password in this entry is then used for authentication of the user. The shadow file can only be read by the privileged utility pwdauth(8), so that the encrypted passwords in the shadow file are kept secret, and thus safe from a dictionary attack. Special password and group file entries There are several entries in the password and group files that are preallocated for current or future use. All id's less than 10 are reserved. The special password file entries are: root:##root:0:0:Big Brother:/usr/src: daemon:*:1:1:The Deuce:/etc: bin:##root:2:0:Binaries:/usr/src: uucp:*:5:5:UNIX to UNIX copy:/usr/spool/uucp:/usr/sbin/uucico news:*:6:6:Usenet news:/usr/spool/news: ftp:*:7:7:Anonymous FTP:/usr/ftp: nobody:*:9999:99::/tmp: ast:*:8:3:Andrew S. Tanenbaum:/usr/ast: The root id is of course the super user. The daemon id is used by some daemons. Some devices are protected so that only those daemons can access them. The bin id owns all sources and most binaries. The uucp, news and ftp id's are for serial line data transfer, usenet news, or ftp if so needed. The nobody id is used in those cases that a program may not have any privileges at all. The ast id is the honorary home directory for Andrew S. Tanenbaum, the creator of Minix. You can also find the initial contents for a new home directory there. The special group file entries are: operator:*:0: daemon:*:1: bin:*:2: other:*:3: tty:*:4: uucp:*:5: news:*:6: ftp:*:7: kmem:*:8: nogroup:*:99: Groups with the same name as special user id are used with those id's. The operator group is for the administrators of the system. Users in this group are granted special privileges. The other group is for ordinary users. The tty group is for terminal devices, and associ- ated set-gid commands. Same thing with the kmem group and memory devices. FILES
/etc/passwd The user database. /etc/group The group database. /etc/shadow The shadow password file. SEE ALSO
login(1), passwd(1), su(1), crypt(3), getpwent(3), getgrent(3), pwdauth(8). NOTES
The nobody and nogroup id's are likely to be renumbered to the highest possible id's once it is figured out what they are. AUTHOR
Kees J. Bot (kjb@cs.vu.nl) PASSWD(5)
All times are GMT -4. The time now is 01:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy