Re: Way to auto-set all users' screens to NOT go idle/lock?

On 2019-01-14, Dashamir Hoxha wrote:
> On Mon, Jan 14, 2019 at 2:14 AM David Groos <[email protected]> wrote:
>> *LDM_PASSWORD_HASH*
>>            boolean, default *False*
>>
>>            When set to *True*, this will create a proper shadow entry on the client, allowing for
>>            screen locking, and other things which require authentication to work. Note, this
>>            allows you to change your password locally, or possibly other actions such as sudo,
>>            but these changes are only temporary and will not persist on reboot.
>>
> I said that it is a common solution because I have seen the issue of
> screen locking several times on this list, and everybody suggests this
> solution (we may also say that this is a frequently raised issue).
> I even wonder why the default value of this option is not 'True'? Why is it
> more useful to have it disabled than to have it enabled?

Since it requires much more code touching live password data, and
storing a hash of the password in an additional location, it's a bit of
a security concern. So it's a classic trade-off for security
vs. convenience, and thus opt-in by default.

live well,
  vagrant

_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCXDziPAAKCRDcUY/If5cW
qgeLAP9oj4ZGU96sqAHAGDyP0877lJ31rTlIgCJK+4Pwv1KsRQD9EPR0I6lIPAMC
tVm1+dVOzgPIaGbh9TN2RTn+1FfInw0=
=FNmQ
-----END PGP SIGNATURE-----