05-17-2013
Passwd Utility Corrupted
I have a legacy Solaris 8 machine. Someone has overwitten the passwd utility so I now can't change passwords.
Is there somwhere I can download a copy? I do have the installation CDs as well.
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I know I saw a couple posts about this a long time ago, but could not find them with search. Please refresh my memory.
-Chuck (1 Reply)
Discussion started by: 98_1LE
1 Replies
2. HP-UX
Good Day
Our HP box was hacked and the passwd file has been altered,there are only 2 user accounts active,and these dont have any administrative rights.I need to edit the passwd file to correct the su and root entries.
Does any body have any suggestions as to how i can do this with out the root... (10 Replies)
Discussion started by: cantona7
10 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I am new to UNIX, and have recently installed Suse 9.3. I have been experimenting with all of the commands and have somehow managed to modify the default shell of the root user to an invalid file. Consequently I cannot su to the root user as I receive the 'no such file or directory' error... (2 Replies)
Discussion started by: Tony Montana
2 Replies
4. AIX
I'm getting the following error after we replaced a failed disk in a mirrored logical volume. We cleared the device entry in ODM before adding the new disk but when we create the mirror we get the following error after running lslv.
0516-022 lslv: Illegal parameter or structure value.... (1 Reply)
Discussion started by: Alfredo Jimenez
1 Replies
5. Shell Programming and Scripting
Hi,
I need to zip/compress a data file and send to a vendor. The vendor does have only unzip utility and can accept only .ZIP files. I do not have zip utility in my server.
How do I zip/compress the file so that it can be deflated using unzip command ? I tried gzip & compress commands, but... (1 Reply)
Discussion started by: Sabari Nath S
1 Replies
6. Red Hat
I accidentally changed root shell from /bin/bash to bash in /etc/password, then logged out from root. Now I can't login as root and got "No shell" error, although I have root password. "su -f -s /bin/bash" command does NOT work. There is no GUI interface for this system.
My question: Do I have... (7 Replies)
Discussion started by: aixlover
7 Replies
7. Emergency UNIX and Linux Support
Hi all ,
i have an issue in netra 20 server
when i boot the system its getting rebooting
and it is giving tha" /etc/name_to_sysnum " file not found
i done
OK> boot -ar
then also not solved
please can any body send the answer ASAP
regards (3 Replies)
Discussion started by: wkbn86
3 Replies
8. Solaris
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
9. AIX
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
10. UNIX for Advanced & Expert Users
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
LEARN ABOUT OSX
master.passwd
PASSWD(5) BSD File Formats Manual PASSWD(5)
NAME
passwd, master.passwd -- format of the password file
DESCRIPTION
The /etc/passwd file is a legacy BSD 4.3 format file. It is mostly unused, but is updated by some utility programs. Its format is similar
to the /etc/master.passwd file, except that it does not contain the class, change, and expire fields described below.
The /etc/master.passwd file comprises newline separated records, one per user. Each line contains ten colon (``:'') separated fields. These
fields are as follows:
name User's login name.
password User's encrypted password.
uid User's id.
gid User's login group id.
class User's general classification (unused).
change Password change time.
expire Account expiration time.
gecos User's full name.
home_dir User's home directory.
shell User's login shell.
The name field is the login used to access the computer account, and the uid field is the number associated with it. They should both be
unique across the system (and often across a group of systems) since they control file access.
While it is possible to have multiple entries with identical login names and/or identical user id's, it is usually a mistake to do so. Rou-
tines that manipulate these files will often return only one of the multiple entries, and that one by random selection.
The login name must never begin with a hyphen (``-''); also, it is strongly suggested that neither upper-case characters or dots (``.'') be
part of the name, as this tends to confuse mailers. No field may contain a colon (``:'') as this has been used historically to separate the
fields in the user database.
The password field is the encrypted form of the password. If the password field is empty, no password will be required to gain access to the
machine. This is almost invariably a mistake. Because these files contain the encrypted user passwords, they should not be readable by any-
one without appropriate privileges.
The group field is the group that the user will be placed in upon login. Since this system supports multiple groups (see groups(1)) this
field currently has little special meaning.
The class field is currently unused.
The change field is the number in seconds, GMT, from the epoch, until the password for the account must be changed. This field may be left
empty to turn off the password aging feature.
The expire field is the number in seconds, GMT, from the epoch, until the account expires. This field may be left empty to turn off the
account aging feature.
The gecos field normally contains the user's full name. Note that Mac OS X differs from some other operating systems, where the gecos field
may contain other comma-separcted information about the user.
The home_dir field is the user's home directory. This is the full path name where the user will be placed on login.
The shell field is the command interpreter the user prefers. If there is nothing in the shell field, the Bourne shell (/bin/sh) is assumed.
INTERACTION WITH DIRECTORY SERVICES
Processes generally find user records using one of the getpwent(3) family of functions. On Mac OS X, these functions interact with the
DirectoryService(8) daemon, which reads the /etc/master.passwd file as well as searching other directory information services to find user
accounts.
FILES
/etc/passwd
/etc/master.passwd
SEE ALSO
chpass(1), login(1), passwd(1), getpwent(3), netgroup(5), DirectoryService(8), pwd_mkdb(8), vipw(8)
HISTORY
A passwd file format appeared in Version 6 AT&T UNIX.
BSD
July 18, 1995 BSD