Under F9, I want to create an account such that the user will be required to change the password on login, but I don't have control over how soon (or late) the user will get to that first login. Is there a way to do it? The passwd command didn't look like it had anything useful.
TIA
On Tue, Oct 28, 2008 at 10:15, Steven W. Orr steveo@syslang.net wrote:
Under F9, I want to create an account such that the user will be required to change the password on login, but I don't have control over how soon (or late) the user will get to that first login. Is there a way to do it? The passwd command didn't look like it had anything useful.
TIA
I've used the Gnome and KDE User Account GUI's to do this when I was setting up a second account for the boy to use - when you set the password, there's a ticky box to force the user to change the password on the first login. You set it to expire the password and set the number of logins before forced to change to 0.
amy
On Tue, Oct 28, 2008 at 10:15 AM, Steven W. Orr steveo@syslang.net wrote:
Under F9, I want to create an account such that the user will be required to change the password on login, but I don't have control over how soon (or late) the user will get to that first login. Is there a way to do it? The passwd command didn't look like it had anything useful.
TIA
as root at the CLI: # chage -d 01/01/1970 <someUser> The user will be prompted to change his password next login.
~af
Steven W. Orr wrote:
Under F9, I want to create an account such that the user will be required to change the password on login, but I don't have control over how soon (or late) the user will get to that first login. Is there a way to do it? The passwd command didn't look like it had anything useful.
You can use "usermod -f -1 -e YYYY-MM-DD
The "-f -1" says that the account is never locked, but the "-e YYYY-MM-DD" says "the password expired on year YYYY, month MM and day DD". If you set that to today, e.g.
usermod -f -1 -e 2008-10-28 fred
user fred will have to change his password on the next login. See "man usermod" for details. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer ricks@nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Memory is the second thing to go, but I can't remember the first! - ----------------------------------------------------------------------
Aldo Foot wrote:
On Tue, Oct 28, 2008 at 10:15 AM, Steven W. Orr steveo@syslang.net wrote:
Under F9, I want to create an account such that the user will be required to change the password on login, but I don't have control over how soon (or late) the user will get to that first login. Is there a way to do it? The passwd command didn't look like it had anything useful.
TIA
as root at the CLI: # chage -d 01/01/1970 <someUser> The user will be prompted to change his password next login.
Yeah, that works too. Rats! Why couldn't I remember that one! Yet another senior moment at work! ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer ricks@nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Okay, who put a "stop payment" on my reality check? - ----------------------------------------------------------------------
Quoting Rick Stevens ricks@nerd.com:
Aldo Foot wrote:
On Tue, Oct 28, 2008 at 10:15 AM, Steven W. Orr steveo@syslang.net wrote:
Under F9, I want to create an account such that the user will be required to change the password on login, but I don't have control over how soon (or late) the user will get to that first login. Is there a way to do it? The passwd command didn't look like it had anything useful.
TIA
as root at the CLI: # chage -d 01/01/1970 <someUser> The user will be prompted to change his password next login.
Yeah, that works too. Rats! Why couldn't I remember that one! Yet another senior moment at work!
hmmm ... i interpreted the OP's question as asking how to force a new user to set a password on first login, but *also* to put a time limit on how long that person had to log in before the account was locked.
as in, if a new user is too lazy to log in to a new account, then after a week of complete non-use, it locks automatically. as long as the user gets to it before then, they have to set a new password, after which they're good to go.
was this addressed?
rday
On Tuesday, Oct 28th 2008 at 14:00 -0000, quoth Robert P. J. Day:
=>Quoting Rick Stevens ricks@nerd.com: => =>> Aldo Foot wrote: =>> > On Tue, Oct 28, 2008 at 10:15 AM, Steven W. Orr steveo@syslang.net =>> > wrote: =>> > > Under F9, I want to create an account such that the user will be =>> > > required to =>> > > change the password on login, but I don't have control over how soon (or =>> > > late) the user will get to that first login. Is there a way to do it? =>> > > The =>> > > passwd command didn't look like it had anything useful. =>> > > =>> > > TIA =>> > > =>> > =>> > as root at the CLI: =>> > # chage -d 01/01/1970 <someUser> =>> > The user will be prompted to change his password next login. =>> =>> Yeah, that works too. Rats! Why couldn't I remember that one! Yet =>> another senior moment at work! => => hmmm ... i interpreted the OP's question as asking how to force a new =>user to set a password on first login, but *also* to put a time limit =>on how long that person had to log in before the account was locked. => => as in, if a new user is too lazy to log in to a new account, then =>after a week of complete non-use, it locks automatically. as long =>as the user gets to it before then, they have to set a new password, =>after which they're good to go. => => was this addressed?
Thanks Robert, Actually, I'm shooting for something different.
The passwords on this machine never expire and that's the way I want it. What I want to add is for all of the *new* accounts to cause a forced reset of the password at first login, no matter how long it takes for them to get to logging in. Everyone's initial password is (something like) ChangeMeOnLogin and I just don't want those to persist.
On Tue, Oct 28, 2008 at 10:57 AM, Rick Stevens ricks@nerd.com wrote:
Yeah, that works too. Rats! Why couldn't I remember that one! Yet another senior moment at work!
That's not too bad... as when I have my car keys in my left hand and I keep wondering where I put them. :-)
~af
On Tuesday, Oct 28th 2008 at 13:51 -0000, quoth Rick Stevens:
=>Steven W. Orr wrote: =>> Under F9, I want to create an account such that the user will be required to =>> change the password on login, but I don't have control over how soon (or =>> late) the user will get to that first login. Is there a way to do it? The =>> passwd command didn't look like it had anything useful. => =>You can use "usermod -f -1 -e YYYY-MM-DD => =>The "-f -1" says that the account is never locked, but the "-e =>YYYY-MM-DD" says "the password expired on year YYYY, month MM and day =>DD". If you set that to today, e.g. => => usermod -f -1 -e 2008-10-28 fred => =>user fred will have to change his password on the next login. See =>"man usermod" for details.
Bingo. Thanks. :-)
On Tue, 2008-10-28 at 14:30 -0400, Steven W. Orr wrote:
What I want to add is for all of the *new* accounts to cause a forced reset of the password at first login, no matter how long it takes for them to get to logging in. Everyone's initial password is (something like) ChangeMeOnLogin and I just don't want those to persist.
When doing things like that, don't forget that some people won't know how to change their passwords. Some people barely manage to type their own name to log on... I had great fun ribbing mum about that the other week.
Tim wrote:
On Tue, 2008-10-28 at 14:30 -0400, Steven W. Orr wrote:
What I want to add is for all of the *new* accounts to cause a forced reset of the password at first login, no matter how long it takes for them to get to logging in. Everyone's initial password is (something like) ChangeMeOnLogin and I just don't want those to persist.
When doing things like that, don't forget that some people won't know how to change their passwords. Some people barely manage to type their own name to log on... I had great fun ribbing mum about that the other week.
We have always set-up new users and their restriction on an individual basis. This is also the same for MS products. What else do you need? You can copy an individuals permissions but passwords are always based on an individual account creation.