Sponsored Content
Operating Systems Solaris passwd cmd reenables passwd aging in shadow entry Post 302485219 by sboots on Tuesday 4th of January 2011 02:34:08 PM
Old 01-04-2011
Code:
passwd -x -1 username

has to be ran as root i believe.

If you want it to persist through password changes then script it and put it in roots crontab with all users that you want to not be required to change their passwords. Something like this. As far as i know there is no other way to do it, but i may be wrong.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Cron job failure - passwd aging feature

I have a script running as a cron job in machine A . This script ftps some files everyday from machine A to machine B, and mails me about the status. It works fine for some days....and suddenly stops running. By viewing the log files, I see that the script itself was not invoked by cron on those... (4 Replies)
Discussion started by: Deepa
4 Replies

2. UNIX for Dummies Questions & Answers

How to : Identify the the password is encrypted or not in /etc/shadow or /etc/passwd?

Thanks AVKlinux (11 Replies)
Discussion started by: avklinux
11 Replies

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

4. Solaris

tool to convert /etc/passwd and etc/shadow

i wonder if there is a tool to read the /etc/passwd or /etc/shadow files in order to reset user accounts to the same one. By moving (restore) all filessytem and data to another same Sun box, none of the users are able to logon to the new box which i didn't change nothing. But if i reset the user... (1 Reply)
Discussion started by: lamoul
1 Replies

5. UNIX for Advanced & Expert Users

Converting freebsd (5.2.1) master.passwd to Debian shadow

I'm trying to make this work, and it half works. Accounts with password hashes matching the old crypt(3) algorithm work just fine: JUpfW/w6jo6aw But accounts with longer password hashes preceded by $1$, such as the following, do not work: $1$iIcbppdP$HDyjJeVMGgJ.ovLsnjtTR.... (0 Replies)
Discussion started by: davidstvz
0 Replies

6. Red Hat

how passwd cmd is working

how unix users able to change their password even if they have only read permissions and how backend process will be happening can u explain me which are files need to involved in this process (3 Replies)
Discussion started by: ponmuthu
3 Replies

7. Solaris

difference between /etc/shadow and /etc/default/passwd

Hi , can anyone explain me the difference between /etc/shadow and /etc/default/passwd . As per my knowledge both the files are used for password aging and control parameters. (2 Replies)
Discussion started by: rogerben
2 Replies

8. UNIX for Advanced & Expert Users

psswd&shadow 2 passwd together?!!

hi, all I just started on new box where I have to diff passwd working perfectly on the very same account/user. I see that shadow was added recently (I'm not a root in there), I see 'x' in passwd. Not sure how it should work, should I change old passwd for one defined in shadow? Or it's fine to... (20 Replies)
Discussion started by: trento17
20 Replies

9. Solaris

Passwd,shadow files deleted and abort sequence disabled

Hi all.. I moved the /etc/shadow and /etc/shadow files to /tmp and then rebooted my PARC machine running 5.10. I did it to see if I could recover from single user mode. But, I forgot to enable the abort key-sequence which I earlier disabled. Stuck! One of my gurus told I had to... (9 Replies)
Discussion started by: satish51392111
9 Replies

10. Solaris

Passwd -l or -u modifies lastchg field in /etc/shadow file

Hi, I have a Solaris 10 box where password aging is not functioning properly. Using the passwd command with the -l or -u options causes the lastchg field in the /etc/shadow file to be modified. Therefore, if a user's password is set to expire in 90 days and they are 1 day away, all they have... (4 Replies)
Discussion started by: cschar
4 Replies
lppasswd(1)						      Easy Software Products						       lppasswd(1)

NAME
lppasswd - add, change, or delete digest passwords. SYNOPSIS
lppasswd [ -a ] [ -g groupname ] [ -x ] [ username ] DESCRIPTION
lppasswd adds, changes, or deletes passwords in the CUPS digest password file, passwd.md5. When run by a normal user, lppasswd will prompt for the old and new passwords. When run by the super-user, lppasswd can add new accounts (-a username), change existing accounts (user- name), or delete accounts (-x username) in the digest password file. Digest usernames do not have to match local UNIX usernames, but only UNIX usernames are supported by the CUPS client programs (lp(1), lpr(1), etc.) The -g option specifies a group other than the system group - "sys", "system", or "root", depending on the operating system. SECURITY ISSUES
The lppasswd command is installed setuid to root. While every attempt has been made to make it secure against exploits that could grant super-user priviledges to unpriviledged users, paranoid system administrators may wish to disable or change the ownership of the program to an unpriviledged account. SEE ALSO
lp(1), lpr(1), CUPS Software Administrators Manual, CUPS Software Users Manual, http://localhost:631/documentation.html COPYRIGHT
Copyright 1993-2002 by Easy Software Products, All Rights Reserved. 7 June 2001 Common UNIX Printing System lppasswd(1)
All times are GMT -4. The time now is 10:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy