Passwd -f locks out login


 
Thread Tools Search this Thread
Operating Systems Solaris Passwd -f locks out login
# 1  
Old 06-18-2014
Passwd -f locks out login

hello;

I have inherited a SunOS sjcorpftp 5.10 Generic_118855-36 i86pc i386 i86pc

whenever someone needs a new password, I change it via
Code:
"passwd username"

then
Code:
"passwd -f username"  so they can change their password

on my only sun sparc 5.9 you can "accessed denied" when you login as username

anyone seen this before

thanks much

Last edited by vbe; 06-18-2014 at 12:55 PM.. Reason: code tags please
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Why unix passwd are hidden when while login

Hi, I might be stupid here to ask such question but I was just curious on ssh login to unix boxes (solaris). When we login to unix box, it asks for password, but while typing the password, the password characters (like asterik or anything) seems hidden. why it is so? Thanks (3 Replies)
Discussion started by: snchaudhari2
3 Replies

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

3. Shell Programming and Scripting

Issue in passing passwd to login into a sudo account

Hi Gurus, I have small issue... I used to pass the passwd for sudo commands like below, gzcat ~/passwd.gz | sudo su - <villin> >> eof ------ ----- ------ eof And it was able to login into "villin" sudo account successfully. But now, I'm using the same in another script for the... (2 Replies)
Discussion started by: raghu.iv85
2 Replies

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

5. Solaris

Solaris 10 allow ssh login with empty passwd

I have turned off PermitEmptyPasswords in sshd_config, but a user with empty passwd (deleted by passwd -d user) can still login without password, why? it is big security concern, linux doesn't have the issue. $ uname -a SunOS 5.10 Generic_118855-14 i86pc i386 i86pc ... (8 Replies)
Discussion started by: honglus
8 Replies

6. Solaris

Force user to change passwd on first login

Hello All, How to force user to change his login passwd on his first login in solaris 10 ? while adding user do we need to set the password in theis case?? (7 Replies)
Discussion started by: saurabh84g
7 Replies

7. UNIX for Advanced & Expert Users

current locks on a file

I want to know all the locks on a file - read, write etc acquired by various processes. Is there any way to know ? (2 Replies)
Discussion started by: radiatejava
2 Replies

8. Linux

Whats for: /etc/locks directory?

Hi there! Can someone please tell me what is for the directory /etc/locks and provide me with an example. I certainly don't understand it very well. Any help will be much appreciated! (1 Reply)
Discussion started by: agasamapetilon
1 Replies

9. HP-UX

File Locks

Hi, How to list the files which are not locked? I want to read the files that are not locked by other user only. can we do it using ls option? (5 Replies)
Discussion started by: vijaykrc
5 Replies

10. HP-UX

Login to diff server w/o prompts for passwd

Is there any way to login to another server with out getting prompted for the password? Is there a way to embed the password in a script and use either telnet or rlogin (or some other prg)? I need to do some file manipulation on several servers for out ORACLE 10g RAC and need to automated so... (4 Replies)
Discussion started by: vslewis
4 Replies
Login or Register to Ask a Question
PASSWD(5)							File Formats Manual							 PASSWD(5)

NAME
passwd - password files DESCRIPTION
Passwd files are files consisting of newline separated records, one per user, containing 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 general information about the user 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. Routines 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 anyone 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. In the near future it will be a key to a termcap(5) style database of user attributes. 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 comma (``,'') separated subfields as follows: name user's full name office user's office number wphone user's work phone number hphone user's home phone number This information is used by the finger(1) program. The user's home directory is the full UNIX path name where the user will be placed on login. The shell field is the command interpreter the user prefers. If the shell field is empty, the Bourne shell (/bin/sh) is assumed. SEE ALSO
chpass(1), login(1), passwd(1), getpwent(3), mkpasswd(8), vipw(8) adduser(8) BUGS
User information should (and eventually will) be stored elsewhere. 7th Edition May 8, 1989 PASSWD(5)