From: "Eve Atley" <eatley@wowcorp.com>
To: John Kelly <bilbo@waitrose.com>, linux-newbie@vger.kernel.org
Subject: RE: ssh setup: user 'locked out' daily
Date: Thu, 19 Aug 2004 14:54:19 -0400 [thread overview]
Message-ID: <GNEPLLCIIBHICCOGIAKPEEEADDAA.eatley@wowcorp.com> (raw)
In-Reply-To: <20040819171227.21e76e1c.bilbo@waitrose.com>
Thanks for the reply!
Ok, I did some looking, and chage pulls up the following info (with user
'emon' being one of the problematic ones, and user 'eve' being an old
account):
[root@wow-rtr etc]# chage -l emon
Minimum: -1
Maximum: 99999
Warning: -1
Inactive: -1
Last Change: Aug 19, 2004
Password Expires: Never
Password Inactive: Never
Account Expires: Never
[root@wow-rtr etc]# chage -l eve
Minimum: 0
Maximum: 0
Warning: 7
Inactive: 0
Last Change: Feb 03, 2004
Password Expires: Never
Password Inactive: Never
Account Expires: Never
[root@wow-rtr etc]#
The odd thing is that previous to my change (using a kewl graphical tool) of
removing the password expiration, user 'emon' looked just the same as user
'eve' which was set up quite some time ago.
I set up user 'emon' the same was as 2 previous users, and they have not
expired!
- Eve
-----Original Message-----
From: linux-newbie-owner@vger.kernel.org
[mailto:linux-newbie-owner@vger.kernel.org]On Behalf Of John Kelly
Sent: Thursday, August 19, 2004 12:12 PM
To: linux-newbie@vger.kernel.org
Subject: Re: ssh setup: user 'locked out' daily
Hi,
On Thu, 19 Aug 2004 11:13:22 -0400
"Eve Atley" <eatley@wowcorp.com> wrote:
>
> We have SSH running on our Linux Redhat 9 server. I set up new users
> to dump them upon initial login to a common directory using the
> following command: useradd -M -d /home/shared username -p password
> passwd username (for some reason, -p password doesn't work?)
>
> On a daily basis, they are locked out. /var/log/secure indicates the
> following:
> fatal: monitor_read: unsupported request: 24
> PAM rejected by account configuration[13]: User account has
> expired
>
> /var/log indicates the following:
> Aug 19 10:38:15 wow-rtr sshd(pam_unix)[19144]: account emon has
> expired(failed to change password)
>
> They log in with winscp3 (graphical client) using sftp.
>
I haven't looked at RedHat since 7.3 but ...
The problem here seems simple enough - the user account has expired.
Have a look at the man page for passwd and in particular the -x -n -w
-i options. There is also a program called chage which changes the
account ageing details. Account expiry information is held in
/etc/shadow - the manpage for shadow explains how it works.
I believe that there is a file in /etc/system/ or /etc/sysconfig/ (I
am not sure of the name) on RedHat which sets the default
password/account ageing policy. You may have to edit this file so
that newly created accounts don't expire. There may even be a kewl
graphical tool to do this - I haven't looked at RedHat recently and I
don't use kewl graphically tools anyway :-).
Hope this helps.
regards,
John Kelly
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-08-19 18:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 21:12 upgrading open ssh Anna G. Zapata
2004-02-23 21:30 ` Armen Kaleshian
2004-02-23 22:03 ` Anna G. Zapata
2004-02-23 22:52 ` Armen Kaleshian
2004-08-19 15:13 ` ssh setup: user 'locked out' daily Eve Atley
2004-08-19 16:12 ` John Kelly
2004-08-19 18:54 ` Eve Atley [this message]
2004-09-08 5:27 ` -p option for useradd ( was Re: ssh setup: user 'locked out' daily ) Stephen Samuel
2004-12-22 15:38 ` Interpreting disk space and changing backup path Eve Atley
2004-12-22 16:28 ` Ray Olszewski
2004-12-22 20:37 ` qwms-avib
2004-02-23 21:44 ` upgrading open ssh Ray Olszewski
2004-02-23 21:45 ` caszonyi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=GNEPLLCIIBHICCOGIAKPEEEADDAA.eatley@wowcorp.com \
--to=eatley@wowcorp.com \
--cc=bilbo@waitrose.com \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.