Yes, this is what I'm talking about. Thanks for the information. I
was experiencing a problem yesterday which may have something to do
with password aging. I logged in single user mode, changed the
passwords of the accounts I was trying to access and received
"Authorization Failed" when trying to login. What solved the problem,
or temporarily at least, was to delete the user and their home
directory then recreate them. After this they were able to login.
On Jan 23, 2006, at 5:00 PM, george chamales wrote:
> Hi Ken,
>
> I'm working with the Project on the ability to create customized
> honeywall isos. You should be hearing back from them on this pretty
> soon.
>
> Password aging is set using the chage commande which is called on
> line 525 of /usr/local/bin/lockdown-hw.sh. That script is called
> by rc.local the first time the honywall is booted after the
> initial install. Once the script has been run rc.local touches the
> file /etc/locked.down. If that file exists rc.local won't call
> lockdown-hw.sh again.
>
> ####################################################################
> #Set up password aging
> for NAME in $(cut -f1 -d':' /etc/passwd); do
> NAME_UID=$(id -u ${NAME})
> if [ "${NAME_UID}" -ge 500 -a "${NAME_UID}" != 65534 ]; then
> /usr/bin/chage -m 0 -M 90 -W 25 -I 900 ${NAME}
> fi
> done
> ####################################################################
>
> Hope this help,
> george
>
>
>
> On Mon, Jan 23, 2006 at 03:25:05PM -0500, Ken Garland wrote:
>> We are running Roo on one of our networks and from time to time the
>> root password will just stop working. Same with the default roo
>> account. Is there a default password expire time setup with Roo?
Received on Jan 25 2006
Intro
