AW: Lock Account

• Previous message: John Mendenhall: "Re: OpenSSH_3.5p1 server, some PC clients cannot connect"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Date: Tue, 25 Feb 2003 16:17:59 +0100
From: "openssh" <Openssh@lists.netways.de>
To: <secureshell@securityfocus.com>

Easiest way with the usage of shadow is :

Usermod -L username --> keyfile auth will still work -> passwd login won´t

>-----Ursprüngliche Nachricht-----
>Von: Parsons, Rick [mailto:rick.parsons@eds.com]
>Bereitgestellt: Montag, 24. Februar 2003 17:20
>Bereitgestellt in: openssh
>Unterhaltung: Lock Account
>Betreff: RE: Lock Account
>
>
>James said ...
>
>> Another drawback to this method is that now all the files that were
>> previously owned by "miguel" are now owned by "*miguel", potentially
>> creating confusion.
>
>Only because it stores owner's of files by UID's and checks
>/etc/passwd
>for the username string associated with that UID. If you
>change *miguel
>back to miguel, everything is owned by miguel again. It's important to
>not mislead people into thinking major system changes have
>occured when
>they actually have not.
>
>---- My point precisely. That is why you shouldn't do it.
>
>Rick Parsons
>
>Bristol, England
>

• Next message: Martinez, Michael - CSREES/ISTM: "RE: OpenSSH_3.5p1 server, some PC clients cannot connect"
• Previous message: John Mendenhall: "Re: OpenSSH_3.5p1 server, some PC clients cannot connect"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]