No i am sure the entry is same on both /etc/passwd and /etc/shadow files.
If that's how your shadow file looks, then you're in trouble. Stuff like group membership and login shell are what gets stored in /etc/passwd. The fields in /etc/shadow should all be related to password policy and password hashes. I'm willing to bet they both came from /etc/passwd otherwise your system would be in total failure and that would probably take
It's probably better to focus on _why_ you're interested in getting rid of passwords. If it's to get scripted access to this account from a remote system, you can set up passwordless ssh. If it's for scripted access to the account locally, use sudo.
If it's just to keep from having to enter your password at the login prompt you may ask whether this is really something you want to do and if so just blanking out the hash field will get you out of entering a password on most systems.
For example, where you have:
or
Should become:
I've only tested this on logging into the desktop and from a TTY. Logging in remotely can be taken care of the other way (via ssh) though.
Hello out there in unix.com land. I am Cerberus and this is my first post. I am brand new to Unix and i have a quesiton for you all.
Relating to the Unix Password File Setup, what is:
User ID?
Password?
any insite comparing one to the other as far as specifics would be greatly... (2 Replies)
Hi Everybody
I want to write a script in solaris that will add user and set his password. How I will do that.
Moreover, if anybody knows where can i find documentation, material and downloads for sample scripts in solaris then please tell me.
Thanx
Ehsan (1 Reply)
hello i have some probelm in the Unix Sun system ....so anyone can u help me how to sovle the problem :
1.how to add the user name and password.
2.list out the command..
Thank You (1 Reply)
I have two unix server ( eg. they are Server A , Server B ) and want to use LDAP to control the user profile , each of these servers have some database and application are running , assume I have setup Server A as LDAP server . Now I am not too understand the practice of it, could anyone can advise... (0 Replies)
I just installed Solaris 10 yesterday and I need to create a new username and password. I'm new to the system and I have yet to learn my way around. I appreciate all help and thank you in advance. (5 Replies)
Helo ,
I m using linux pam library for user and its password authentication.
I m creating new user and giving its password.I m giving password of 10 characters.now when I login in as that newly created user its ask me
$ su - ram
Password:
You are required to change your password immediately... (12 Replies)
I want to switch as another user without using password .Is it posiible ? I have one server B and I have logged in as username u1 but I want to login to that same server using username as u2 but I don't want to give the password for u2. (3 Replies)
Can someone help in writing some script through which I can transfer file (scp) from root user in abc server to crt user in hfg server and can give the crt user password in script itself so that it doesn't prompt me every time for password (4 Replies)
Hello -
I want to reset user password in multiple server via root ID. I have passwordless authentication for root between all the servers.
I an use loop to reset the password. I am using below command in loop
echo mypassword | passwd username --stdin
However, if anyone sees history - he... (5 Replies)
Discussion started by: saurabh84g
5 Replies
LEARN ABOUT REDHAT
passwd
PASSWD(5) File formats PASSWD(5)NAME
passwd - password file
DESCRIPTION
Passwd is a text file, that contains a list of the system's accounts, giving for each account some useful information like user ID, group
ID, home directory, shell, etc. Often, it also contains the encrypted passwords for each account. It should have general read permission
(many utilities, like ls(1) use it to map user IDs to user names), but write access only for the superuser.
In the good old days there was no great problem with this general read permission. Everybody could read the encrypted passwords, but the
hardware was too slow to crack a well-chosen password, and moreover, the basic assumption used to be that of a friendly user-community.
These days many people run some version of the shadow password suite, where /etc/passwd has *'s instead of encrypted passwords, and the
encrypted passwords are in /etc/shadow which is readable by the superuser only.
Regardless of whether shadow passwords are used, many sysadmins use a star in the encrypted password field to make sure that this user can
not authenticate him- or herself using a password. (But see the Notes below.)
If you create a new login, first put a star in the password field, then use passwd(1) to set it.
There is one entry per line, and each line has the format:
account:password:UID:GID:GECOS:directory:shell
The field descriptions are:
account the name of the user on the system. It should not contain capital letters.
password the encrypted user password or a star.
UID the numerical user ID.
GID the numerical primary group ID for this user.
GECOS This field is optional and only used for informational purposes. Usually, it contains the full user name. GECOS means
General Electric Comprehensive Operating System, which has been renamed to GCOS when GE's large systems division was sold
to Honeywell. Dennis Ritchie has reported: "Sometimes we sent printer output or batch jobs to the GCOS machine. The gcos
field in the password file was a place to stash the information for the $IDENTcard. Not elegant."
directory the user's $HOME directory.
shell the program to run at login (if empty, use /bin/sh). If set to a non-existing executable, the user will be unable to
login through login(1).
NOTE
If you want to create user groups, their GIDs must be equal and there must be an entry in /etc/group, or no group will exist.
If the encrypted password is set to a star, the user will be unable to login using login(1), but may still login using rlogin(1), run
existing processes and initiate new ones through rsh(1), cron(1), at(1), or mail filters, etc. Trying to lock an account by simply chang-
ing the shell field yields the same result and additionally allows the use of su(1).
FILES
/etc/passwd
SEE ALSO passwd(1), login(1), su(1), group(5), shadow(5)
1998-01-05 PASSWD(5)