El mar, 07-01-2014 a las 23:42 -0800, Vagrant Cascadian escribió: > On Wed, Jan 08, 2014 at 12:29:32AM -0600, Luis A. Guzmán García wrote: > > I was all day (it's late night right now) trying to set up autologin for > > my ltsp server/thin clients. I'm using LTSP standalone v5.3.7 > ... > > IIRC, there was somewhere that said i could set MAC instead of IP on > > lts.conf > > > > > ====================================================== > > [Default] > > LDM_AUTOLOGIN = True > > > > [01:23:45:67:89:0a] > > LDM_USERNAME = ltsp-01 > > LDM_PASSWORD = user01 > > By default, it will automatically log in with the hostname as the username and > password, which will typically be "ltspN" where N is a number based on the ip > address (i.e. with ip address range: 10.10.10.20 10.10.10.250, it'll be > 20-250, > unless your netmask is something other than 255.255.255.0). So I typically set > up ltsp users for all the possible account names, and let LDM use the default > Username and Password.
I should specify that i'm running a Ubuntu 12.04 derivate, where i have
built the server and images for the clients.
It's another approach that i haven't thought, but what about session
configurations or files from that session?, if dhcp changes the ip for
the client, hence the user, and all data will be gone, until next time
that it starts on the same user/ip (in the case it saves data from it).
So, to be clear. If i understand correctly,
If i set a bunch of users and passwds inside the subnet range (on
lts.conf), LDM will pick randomly to start a session with that user and
password.
>
> The setup I use also doesn't actually use passwords at all:
>
> You might consider using ssh keys instead of passwords, otherwise the users
> could accidentally or maliciously change the password and lock the screen or
> something. Configure to allow an alternate location for authorized ssh keys in
> /etc/ssh/sshd_config (openssh-server 5.9+):
>
> AuthorizedKeysFile %u/.ssh/authorized_keys
> /var/lib/custom/authorized_keys/%u
>
> Create the ssh key as root, which is what LDM uses to log in, be sure to use
> an
> empty passphrase:
>
> ltsp-chroot ssh-keygen
>
> I prefer not to create homedirs for users who have never logged in, so I use
> pam_mkhommedir. Edit /etc/pam.d/common-auth:
>
> # automatically create new home directories as needed.
> session required pam_mkhomedir.so silent
>
Nice!
> Then create the users, copy the keys into place, lock down the key files (edit
> ARCH and TYPE at least):
>
> pubkey=/opt/ltsp/ARCH/root/.ssh/id_TYPE.pub
> auth_keys_dir=/var/lib/custom/authorized_keys/
> for u in $(seq 20 250); do
> u="ltsp${u}"
> key=${auth_keys_dir}/${u}
> adduser --disabled-password --no-create-home --gecos ,,, ${u}
> cp ${pubkey} ${key}
> chown root:${u} ${key}
> chmod 0640 ${key}
> done
^ ^
^ Where should i put this ^, as shell script, chroot, lts.conf, common-auth?
> There are many other details of things you *could* try, but that's the basic
> configuration that's worked reasonably well for me.
>
Lastly how do you/the user handle saving the files or data achieved
while using the client before that session is over?
Have you tried mounting a folder over network/samba/fstab on the
clients?
> live well,
> vagrant
Thanks for your comments ;)
--
Luis A. Guzmán García
¡Se Libre! - http://fsfla.org/selibre
The Hardware Database Project - http://www.h-node.org
GPG Key: EB153FAF
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_____________________________________________________________________
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
