not able to login to my redhat box as a user

curious_srk · 11-28-2004, 04:07 AM

Hi
I am not able to login to my RH9.0 system as a user.....ok I'll tell you the whole stuff
I had created a username for one guy and then the next day I had changed the superuser password on this system.Now when I try to login as user I am getting the below message.

"Your account has expired; please contact your system administrator su: incorrect password"
su: incorrect password

Does changing the superuser password after creating new user affect the login credentials in any way??I even googled but dint get proper answer.....

plss help

iZvi · 11-28-2004, 05:21 AM

I have changed my root password several times, without affecting anything.
When you setup a new user it asks you for an expiry date. You have probably given something wrong here.

JoshSmith41 · 11-28-2004, 05:32 AM

The only thing I can think of is that you somehow set an expiry date on that account when you changed the password. Or that there is a default expiry date set in the adduser defaults.

From the error message you have provided it looks like you don't have root access.

If not you can use your RH9 boot disk (disk 1) and use the linux rescue option.

From there you can change the root password to gain control.

To check if there is a default expiry value type adduser -D, that should display all defaults.

I have changed the root password many times without anything like that happening.

curious_srk · 11-28-2004, 05:39 AM

Quote:

Originally posted by iZvi
I have changed my root password several times, without affecting anything.
When you setup a new user it asks you for an expiry date. You have probably given something wrong here.

Its not a new machine....It dint ask for any expiry date and there are many other users on this box working without the above problem

curious_srk · 11-28-2004, 05:43 AM

Quote:

Originally posted by JoshSmith41
The only thing I can think of is that you somehow set an expiry date on that account when you changed the password. Or that there is a default expiry date set in the adduser defaults.
From the error message you have provided it looks like you don't have root access.

I am having the root access for this system
How to change the default expiry date?

JoshSmith41 · 11-28-2004, 05:58 AM

useradd -D will show you if you have any defaults.

To change the default expiry date (if you have one):

useradd -D -e null

curious_srk · 11-28-2004, 06:25 AM

Quote:

Originally posted by JoshSmith41
useradd -D will show you if you have any defaults.

To change the default expiry date (if you have one):

Josh
Thank u very much for ur help....meanwhile I had been doing some R&D and found a command called
chage -E <expiry date> Username
this also worked wonderfully....
and it got many options like

chage [-m mindays] [-M maxdays] [-d lastday] [-I inactive]
[-E expiredate] [-W warndays] user

chage -l user
this is used for changing password age of any user........

by the way Josh a small doubt for me again
whats this???? Don't let the TCPA take away your freedom
I was trying to click the link but I was getting page not found

bye
Sri

JoshSmith41 · 11-28-2004, 10:50 AM

Link is working fine for me.

The TCPA stands for the Trusted Computing Platform Alliance which is a group of computer companies which was founded in 1999 by Compaq, HP, IBM, Intel and Microsoft. There are now over 200 other companies with such big names as Adobe, AMD, Fujitsu-Siemens, Gateway, Motorola, Samsung, Toshiba and many others.

The rest is best said by this quote from http://www.againsttcpa.com/what-is-tcpa.html

Quote:

This plans that every computer will have a TPM (Trusted Platform Module), also known as Fritz-Chip, built-in. At later development stages, these functions will be directly included into CPUs, graphiccards, harddisks, soundcards, bios and so on. This will secure that the computer is in a TCPA-conform state and that he checks that it's always in this state. This means: On the first level comes the hardware, on the second comes TCPA and then comes the user. The complete communication works with a 2048 bit strong encryption, so it's also secure enough to make it impossible to decrypt this in realtime for a longer time. This secures that the TCPA can prevent any unwanted software and hardware. The long term result will be that it will be impossible to use hardware and software that's not approved by the TCPA. Presumably there will be high costs to get this certification and that these would be too much for little and mid-range companies. Therefore open-source and freeware would be condemned to die, because without such a certification the software will simply not work. In the long term only the big companies would survive and could control the market as they would like.

I dont know whats happening now but I just wanted to spread the word.