Bug#1008082: How to --lock an account

2022-08-07 Thread Marc Haber
On Sun, Aug 07, 2022 at 01:05:13PM -0400, Jason Franklin wrote: > On Wed, Jul 27, 2022 at 03:21:08PM +0200, Marc Haber wrote: > > > Before I start, I want to make sure we agree on what should be done. > > > > > > I asserted that two things were sufficient: > > > 1. Put a '!' in front of the

Bug#1008082: How to --lock an account

2022-08-07 Thread Jason Franklin
On Wed, Jul 27, 2022 at 03:21:08PM +0200, Marc Haber wrote: > > Before I start, I want to make sure we agree on what should be done. > > > > I asserted that two things were sufficient: > > 1. Put a '!' in front of the user's password in /etc/shadow > > 2. Expire the account > > > > This

Bug#1008082: How to --lock an account

2022-07-28 Thread Marc Haber
[just writing the bug report after realizing that that one forwards to adduser@p.d.o anyway] On Wed, Jul 27, 2022 at 05:52:03PM -0400, Matt Barry wrote: > On Wed, 2022-07-27 at 15:21 +0200, Marc Haber wrote: > > On Wed, Jul 27, 2022 at 09:12:50AM -0400, Jason Franklin wrote: > > For a normal user

Bug#1008082: How to --lock an account

2022-07-27 Thread Matt Barry
On Wed, 2022-07-27 at 15:21 +0200, Marc Haber wrote: > On Wed, Jul 27, 2022 at 09:12:50AM -0400, Jason Franklin wrote: > For a normal user account, I am undecided whether: > > - leave login shell intact, leaving a possible security hole > - set login shell back to the default when the account

Bug#1008082: How to --lock an account

2022-07-27 Thread Marc Haber
On Wed, Jul 27, 2022 at 09:12:50AM -0400, Jason Franklin wrote: > On Wed, Jul 27, 2022 at 12:09:27PM +0200, Marc Haber wrote: > > > > > I think Jason was working on this? > > > > > 1008082/1008084/390457 --system --lock functionality > > > > > > > > I hope so, that should be the next