02-22-2002
After you set them up, you could use the "chage" command to set their last password change back to the beginning of time... (1970-01-01). I suppose they'd have to have password expiry turned on first though... You could have their password expire in some ungodly amount of time that they'll never encounter, though.
I think I've only used linuxconf once, so I don't know if you can do it through there (I stopped using it because it broke stuff when you changed something manually, and in later linuxconf).
Hope someone else can come up with a better idea than that.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
yeah, I tried basically everything I can find from reading books and asking people but I haven't gotten it to work.
is there anything else that can be done. I mean, this internal modem I got is like the last thing I expected Linux not to find (2 Replies)
Discussion started by: TRUEST
2 Replies
2. UNIX for Advanced & Expert Users
Hi,
I notice in my Sun Solaris 8 sparc worstation, I am able to change my password to same existing password.
That is, right now my password is abc, and I change it with "passwd" command and change it abc again. It will accept.
How can I make it such that it will not accept same password?... (3 Replies)
Discussion started by: champion
3 Replies
3. Red Hat
All,
I have a RedHat 9 box which I need to figure out how to get it to stay in full duplex mode after a reboot.
I have tried
ethtool -s eth0 speed 100 duplex full autoneg off
I have tried to add a line to the /etc/sysconfig/network-scripts/ifcfg-eth0 like this:
ETHTOOL_OPTS="speed... (4 Replies)
Discussion started by: bubba112557
4 Replies
4. UNIX for Dummies Questions & Answers
Using Solaris 9 and 10.
What we want to do is set up global rules for our password files to restrict all users, not only new ones set up with the rules but also the ones that have been sitting on the system for years.
Is there a global way to force all users to change their password every 90... (1 Reply)
Discussion started by: LordJezo
1 Replies
5. Shell Programming and Scripting
hi
How can I force user to change of password by modifying the password expiry and the grace period so that the
user has at least 1 week to login and change the password...... (3 Replies)
Discussion started by: tjay83
3 Replies
6. Shell Programming and Scripting
hi
by modifying /etc/shadow
how can I Force a change of password so that user has at least 1 week to login?
I did it by using:
echo "enter username to force password change"
read user;
chage -M 7 $user;
How can I do it by modifying /etc/shadow?? (6 Replies)
Discussion started by: tjay83
6 Replies
7. Red Hat
RHEL 5 update 4. How to force a user to change the password at his next logon.
Thanks in advance. (8 Replies)
Discussion started by: uxadmin007
8 Replies
8. UNIX for Dummies Questions & Answers
I have logged into single user mode and
whenever i issue
passwd root
nothing happens the cursor simply returns back without asking new password.
what can be issue? (5 Replies)
Discussion started by: pinga123
5 Replies
9. Red Hat
Hi expert,
after creating users on Redhat, i wantn to change their password with something that easy to remember and the way we use. For example
#passwd username
hello$123
it don't allow me. It may has something to do /etc/pam.d/filesXXXX there which i don't know to change to allow root... (1 Reply)
Discussion started by: lamoul
1 Replies
10. Forum Support Area for Unregistered Users & Account Problems
I was unable to login and so used the "Forgotten Password' process. I was sent a NEWLY-PROVIDED password and a link through which my password could be changed. The NEWLY-PROVIDED password allowed me to login.
Following the provided link I attempted to update my password to one of my own... (1 Reply)
Discussion started by: Rich Marton
1 Replies
CHAGE(1) User Commands CHAGE(1)
NAME
chage - change user password expiry information
SYNOPSIS
chage [options] LOGIN
DESCRIPTION
The chage command changes the number of days between password changes and the date of the last password change. This information is used by
the system to determine when a user must change his/her password.
OPTIONS
The options which apply to the chage command are:
-d, --lastday LAST_DAY
Set the number of days since January 1st, 1970 when the password was last changed. The date may also be expressed in the format
YYYY-MM-DD (or the format more commonly used in your area).
-E, --expiredate EXPIRE_DATE
Set the date or number of days since January 1, 1970 on which the user's account will no longer be accessible. The date may also be
expressed in the format YYYY-MM-DD (or the format more commonly used in your area). A user whose account is locked must contact the
system administrator before being able to use the system again.
Passing the number -1 as the EXPIRE_DATE will remove an account expiration date.
-h, --help
Display help message and exit.
-I, --inactive INACTIVE
Set the number of days of inactivity after a password has expired before the account is locked. The INACTIVE option is the number of
days of inactivity. A user whose account is locked must contact the system administrator before being able to use the system again.
Passing the number -1 as the INACTIVE will remove an account's inactivity.
-l, --list
Show account aging information.
-m, --mindays MIN_DAYS
Set the minimum number of days between password changes to MIN_DAYS. A value of zero for this field indicates that the user may change
his/her password at any time.
-M, --maxdays MAX_DAYS
Set the maximum number of days during which a password is valid. When MAX_DAYS plus LAST_DAY is less than the current day, the user
will be required to change his/her password before being able to use his/her account. This occurrence can be planned for in advance by
use of the -W option, which provides the user with advance warning.
Passing the number -1 as MAX_DAYS will remove checking a password's validity.
-R, --root CHROOT_DIR
Apply changes in the CHROOT_DIR directory and use the configuration files from the CHROOT_DIR directory.
-W, --warndays WARN_DAYS
Set the number of days of warning before a password change is required. The WARN_DAYS option is the number of days prior to the
password expiring that a user will be warned his/her password is about to expire.
If none of the options are selected, chage operates in an interactive fashion, prompting the user with the current values for all of the
fields. Enter the new value to change the field, or leave the line blank to use the current value. The current value is displayed between a
pair of [ ] marks.
NOTE
The chage program requires a shadow password file to be available.
The chage command is restricted to the root user, except for the -l option, which may be used by an unprivileged user to determine when
his/her password or account is due to expire.
CONFIGURATION
The following configuration variables in /etc/login.defs change the behavior of this tool:
FILES
/etc/passwd
User account information.
/etc/shadow
Secure user account information.
EXIT VALUES
The chage command exits with the following values:
0
success
1
permission denied
2
invalid command syntax
15
can't find the shadow password file
SEE ALSO
passwd(5), shadow(5).
shadow-utils 4.5 01/25/2018 CHAGE(1)