On Thu, 10 Mar 2022 21:25:38 +, Simon McVittie
wrote:
> usermod: unlocking the user's password would result in a passwordless
> account.
> You should set a password with usermod -p to unlock this user's password.
So I can assume that usermod -p will also unlock a previously locked
On Thu, 10 Mar 2022 at 21:18:30 +0100, Marc Haber wrote:
> I have re-read Simon's words and still have the interpretation that
> unlocking an account that has been created with -disabled-login will
> allow login without password, making the account completely open.
That's what I thought would
On Thu, 10 Mar 2022 13:57:13 +0200, Wouter Verhelst
wrote:
>On Wed, Mar 09, 2022 at 09:00:22PM +0100, Marc Haber wrote:
>> On Tue, 8 Mar 2022 18:40:11 +, Simon McVittie
>> >--disabled-login: the new account has an empty password but is "locked";
>> >so password authentication will fail, but
On Wed, Mar 09, 2022 at 09:00:22PM +0100, Marc Haber wrote:
> On Tue, 8 Mar 2022 18:40:11 +, Simon McVittie
> >--disabled-login: the new account has an empty password but is "locked";
> >so password authentication will fail, but "unlocking" the account will
> >result in login being accepted
On Tue, 8 Mar 2022 18:40:11 +, Simon McVittie
wrote:
>On Tue, 08 Mar 2022 at 17:49:04 +0100, Marc Haber wrote:
>> (3)
>> #625758
>> --disabled-password just does not set a password for the newly created
>> account (resulting in '*' in shadow) while --disabled-login places a '!'
>> in shadow.
On Tue, 08 Mar 2022 at 17:49:04 +0100, Marc Haber wrote:
> (3)
> #625758
> --disabled-password just does not set a password for the newly created
> account (resulting in '*' in shadow) while --disabled-login places a '!'
> in shadow. On modern systems with PAM, both variants seem to be
>
6 matches
Mail list logo
