On 05/16/16 10:46, Vagrant Cascadian wrote:
> Up until fairly recently, the LTSP clients had no way of authenticating
> using passphrase credentials. LTSP Thin clients merely logged into the
> server, and LTSP Fat clients (and/or localapps) did some hacks to
> configure the user and group information on the client, but stored no
> authentication credentials.
>
> If the the client is running LDM 2.2.14 or later, you should be able to
> set LDM_PASSWORD_HASH=True in lts.conf, which stores a hash of the
> passphrase used to log in and should allow pam to complete.
>
> If you need a newer version of LDM and/or LTSP, There is a PPA that
> includes newer versions of LTSP and related software:
>
>    https://launchpad.net/~ts.sch.gr/+archive/ubuntu/ppa
>
>
> live well,
>    vagrant
Thanks for the info, my issue was a combination of a few things.

1. I needed LDM_PASSWORD_HASH=True
2. In the /etc/sudoers file, I needed to move my user all the way to the 
bottom; this is why it was still prompting me for my password even 
though I set it to NOPASSWD; the bottom most entry that a user matches 
is the one that is used.
3. I had installed that ppa on the server, but it was after I already 
built my chroot, so my img had the old version in it for LDM.  So I 
added that ppa within the chroot as well as the server and updated it 
and then it worked.

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_____________________________________________________________________
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

Reply via email to