|00:08||staffencasa has left IRC (firstname.lastname@example.org, Ping timeout: 252 seconds)|
|00:25||freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Quit: So long and thanks for all the fish)|
|01:56||gdi2k has left IRC (email@example.com, Ping timeout: 245 seconds)|
|02:09||gdi2k has joined IRC (firstname.lastname@example.org)|
|02:13||gdi2k has left IRC (email@example.com, Ping timeout: 240 seconds)|
|02:31||gdi2k has joined IRC (firstname.lastname@example.org)|
Team, I have a centos 6 setup with ltsp-server 5.4.5-22.el6 all is setup and well. I have notice that my clients hungs on shutting down. Exactly when the device is shuttingdown eth0. It will never power off or reboot. Any ideas how to get pass this small annoyance? :)
|03:18||alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)|
vagrantc: hi, another idea! Instead of reimplementing ldm, how would you feel about using a local 'ltsp-connect' wrapper, which would read ldm_username and ldm_password from ldm.c (i.e. stdin), then call ssh, then create the local user (without exposing ldm_username etc in the environment), and finally would re-ssh as the user to the server?
The difference now is that only 10 shell lines know ldm_username/password from stdin and until the user owned ssh socket is created
Or, if you prefer, all that could be done inside ldm.c...
|03:59||* alkisg thinks the current solution for remoteapps, i.e. having a root listener, is worse, security-wise, than caching the password long enough to do a second ssh connection...|
...and it wastes some more RAM :D
(unrelated): $ grep -r REMOTECMD .
...I don't see REMOTECMD anywhere in the code....
alkisg: that seems like it would be best done in ldm itself, at this point ... but maybe that is too hard.
alkisg: ldm.c (or the ssh plugin ... the c code).
vagrantc: no problem, I've written more .c code than shell code... I just feel .c is not necessary, it just adds overhead for ldm (not the greeter) :)
We still want the local user to be added by our shell script, right?
I.e. ssh.c will call that script before spawning the second ssh connection....
|04:31||* alkisg really doesn't like all that .c => shell => .c => shell swapping...|
With ldm in shell, it would be much more elegant, the greeter in .c, and all the plumbing in shell...
Mixing languages via stdin/stdout is fine, I just don't like it when .c or .py programs continuously call shell commands do to the actual work, and the .c or .py code is just a wrapper that can also be done in shell...
|04:34||* vagrantc nods|
how badly are we doing at that, though, really?
I really think ldm is a bad wrapper for shell scripts that can be done in < 100 lines of shell itself, safely
For rdesktop, it just reads the password from the greeter and puts it in the command line (!)
So the rdesktop plugin could be done in a few lines of shell with no security difference
pam.c doesn't exist, we could do it easily in shell too,
and I don't think reading LDM_PASSWORD from stdin in shell, makes it less secure than reading it from ssh.c....
....and ssh.c can also be done in e.g. 50 lines of code
I could post an ldm in shell for review, without committing anything in trunk...
I think my actual question here is, if I do it well enough (so that it e.g. also supports expired passwords and optionally hashing the password to /etc/shadow which _adds_ security for locking the screen of fat clients), and noone sees any obvious way to exploid LDM_PASSWORD... _then_ would it be OK to push it upstream?
|04:50||* vagrantc is more worried about non-obvious methods|
i am not confident in my ability to spot some of these complicated security issues.
LDM_PASSWORD will be only set between 10 lines of shell code of a single script, not in all of the login scripts...
It won't even be exported to the environment, so cat /proc/pid/environ as root won't see it
Only RAM dumping will, which is the same for any language
And of course anyone with enough rights do dump the RAM could more easily install a keylogger...
The only difference that I see between shell and .c, is that in .c we can call memset to clean the password in RAM. That's very hard to do right, and we don't even try it currently, and (wrt keylogger) I don't even see a point in doing so
alkisg: so, with all the talk of passwords, how would it handle logins with ssh keys?
vagrantc: how is it done now? the user types an empty password, and the sysadmin has somehow allowed him to provide the key to the local filesystem?
alkisg: i don't think it asks for a password unless one is needed
OK, and where is the key?
alkisg: i think it tries the ssh connection before getting the password
when i've set it up, i use /root/.ssh/id*.pub
So the user wouldn't have access to it
only works because ldm runs as root, currently
So, ldm in shell or in c, or even with libpam_sshauth, we couldn't have user-owned ssh socket that way
...unless we copied the keys to some user-owned folder...
i vaguely recally testing it with libpam_sshauth and it worked...
since pam runs as root, and creates the user-owned socket
I don't see how libpam_sshauth can do things that ssh.c or plain shell can't...
To run ssh from the client as the user, the user must exist and have a folder with the keys that he has access to
|05:30||* vagrantc looks at the code, it's been a couple months|
But anyways, back to ldm in .c vs in shell comparison, ldm in shell would do exactly what ldm in .c does now
The exact input/output, the exact file system changes etc
If libpam_sshauth can do better, then maybe we should start with making an libpam_sshauth.c ldm backend...
yeah, ssh keys can't work...
it just runs ssh as the user
So we need to decide if we prefer ssh keys OR a user-owned ssh socket
We could just prefer the keys option...
for autologin, i liked keys better, as i could set up passwordless users on the server
and passwordless users can't do a lot of things, which is exactly how i wanted it
can't change their password, can't authenticate through other means, etc.
OK... so let's abort the user-owned ssh socket plan... rewritting ldm in shell is still a good way to move forward in my opinion
but the user-owned socket is really realyl important!
i wany it all.
someday i'll even be able to type.
The user owned ssh socket is one way to do remoteapps without an extra process binding together 2 sockets
it seems like a lot to invest in when we're looking at switching to something else
It's not any more important than saving 500 Kb RAM on the client...
I'm not sure we'll even want to drop the greeter...
And I don't think it's more than a weekend's work...
i'm just worried about regression potential
How about dropping ldm.c, keeping the greeter, adding libpam_sshauth, and writing a small script to interface between the greeter and libpam_sshauth?
We do have some regression potential there, but we've added libpam_sshauth, which supposedly is the way forward....
if we can sanely integrate libpam_sshauth into ldm, that sounds ideal to me.
|05:46||* alkisg isn't really sure that he prefers libpam_sshauth over e.g. samba, but anyways it's a starting point, having a shell script that allows the greeter to do local pam-based authentication is the key point in my opinion|
|05:46||* vagrantc nods|
ideally, we just support pam... and everything else comes from that.
OK, I'll start with testing libpam_sshauth first, I haven't do so yet... bbl!
i think the ltsp-pam-examples could actually work with something other than libpam_sshautth
thanks for the chat!
|05:47||alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)|
|06:05||freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)|
|06:26||work_alkisg is now known as alkisg|
vagrantc: any how-to's for libpam_sshauth? In a wheezy chroot, can I just install it?
|06:40||alexqwesa has left IRC (email@example.com, Ping timeout: 265 seconds)|
|06:47||alexqwesa has joined IRC (firstname.lastname@example.org)|
https://wiki.ubuntu.com/libpam-sshauth => Unresolved issues: Is Scott smart enough to write this?
|06:50||* alkisg wouldn't wonder about sbalneav1 intelligence, only about if he has enough lobsters to do so...|
50-init-commands: env | sed -n 's/^LTSP_INIT_COMMAND_[0-9][0-9]=//p' | sh
good enough? ^
|07:18||* alkisg will install libpam-sshauth in his trusty box, generate a chroot via ltsp-pnp, and will try to configure libpam_sshauth from LTSP_INIT_COMMAND_xx in order to be able to log in from tty1... brb|
|07:19||alkisg has left IRC (email@example.com, Remote host closed the connection)|
|07:20||work_alkisg has joined IRC (firstname.lastname@example.org)|
|07:20||work_alkisg is now known as alkisg|
|07:26||Fenuks has joined IRC (Fenuks!~Fenuks@184.108.40.206)|
vagrantc: you should package the example ltsp-session in libpam-sshauth's examples...
Ah and since we'll be using libpam_sshauth, there's no reason to delete the tty1 service, it's useful now
you'll have to configure it, but sure
it's got it's own package at the moment
vagrantc: which file do we need to configure? /etc/pam.d/login?
(09:51:13 πμ) vagrantc: it's got it's own package at the moment => /me didn't get that, are you talking about libpam-sshauth?
That's what I installed, but it didn't contain /usr/bin/ltsp-session...
Or at least /usr/share/examples/...ltsp-session
Ah, are you thinking that we should ship /usr/bin/ltsp-session from the ltsp package?
Instead of symlinking it from init-ltsp.d?
i just install the init-ltsp.d hook as part of ltsp-pam
whoops, I didn't install libnss-extrausers... thanks for the link
well, the ltsp-pam package handles that stuff :)
in the current progress section
|08:00||staffencasa has joined IRC (email@example.com)|
vagrantc: in ltsp-pnp, we don't want to modify the server's nss/pam configuration, we want to do those dynamically from init-ltsp.d
Dunno if that affects any of the current ltsp-pam scripts...
i think the ltsp-pam package does everything from init-ltsp.d
or at least it should
long-term, it should be integrated directly into ltsp.
|08:07||staffencasa has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
|08:27||nocturn00 has left IRC (email@example.com, Ping timeout: 245 seconds)|
|08:32||nocturn has joined IRC (nocturn!~nocturn@unaffiliated/nocturn)|
vagrantc: why in pam.d/lightdm, and not in common?
So that it works for tty's too?
alkisg: i.e. you might only want to selectively allow certain services
ok... I copied lightdm to pam.d/login, but a tty login then got stuck in "calling /usr/share/ltsp-pam/ltsp-sesison"...
...after after 1 minute, FAILED LOGIN for guest: system error
|08:42||* alkisg digs more...|
there are probably some parts of that code that aren't meant to be run from arbitrary pam sessions
OK let me see if it works from lightdm, first
|08:54||vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)|
|09:04||bennabiy has left IRC (bennabiy!~Thunderbi@24-181-55-79.dhcp.gnvl.sc.charter.com, Ping timeout: 245 seconds)|
|09:05||bennabiy has joined IRC (bennabiy!~Thunderbi@24-181-55-79.dhcp.gnvl.sc.charter.com)|
|09:09||Fenuks has left IRC (Fenuks!~Fenuks@220.127.116.11, Ping timeout: 246 seconds)|
|10:11||Fenuks has joined IRC (Fenuks!~Fenuks@18.104.22.168)|
|10:26||workingcats has joined IRC (firstname.lastname@example.org)|
|10:28||cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Read error: Connection reset by peer)|
|10:29||cyberorg has joined IRC (email@example.com)|
|10:29||cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)|
|10:47||freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Quit: So long and thanks for all the fish)|
|10:47||hachque has left IRC (hachque!james@2600:3c01::f03c:91ff:fe96:5060, Remote host closed the connection)|
|10:51||hachque has joined IRC (hachque!james@2600:3c01::f03c:91ff:fe96:5060)|
|11:33||Fenuks has left IRC (Fenuks!~Fenuks@22.214.171.124, Ping timeout: 264 seconds)|
|11:34||GrembleBean has joined IRC (GrembleBean!~Ben@cpc35-aztw23-2-0-cust207.18-1.cable.virginm.net)|
|12:22||Yiannis_ has joined IRC (Yiannis_!c23fefeb@gateway/web/freenode/ip.126.96.36.199)|
|12:27||Yiannis_ has left IRC (Yiannis_!c23fefeb@gateway/web/freenode/ip.188.8.131.52, Client Quit)|
Yiannis_: He has fallen asleep ;-)
|12:28||willianmazzardo has joined IRC (firstname.lastname@example.org)|
|12:31||willianmazzardo has left IRC (email@example.com, Client Quit)|
|13:32||alkisg1 has joined IRC (alkisg1!~alkisg@ubuntu/member/alkisg)|
|13:56||cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 250 seconds)|
|13:57||cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)|
cyberorg: congrats about the release ;)
alkisg1, thanks :)
|14:10||gdi2k has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|15:03||mattcen has left IRC (email@example.com, Ping timeout: 257 seconds)|
|15:15||mattcen has joined IRC (firstname.lastname@example.org)|
|15:25||sbalneav1 has left IRC (email@example.com, Quit: WeeChat 0.3.8)|
|15:25||freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)|
|15:25||sbalneav has joined IRC (firstname.lastname@example.org)|
|15:35||staffencasa has joined IRC (email@example.com)|
|15:36||vmlintu has joined IRC (firstname.lastname@example.org)|
|15:37||Fenuks has joined IRC (Fenuks!~Fenuks@184.108.40.206)|
alkisg: alkisg1: I just noticed from the logs that you've been discussing guest logins. I just did a new thin client guest login implementation for our systems last weekend..
There's a inetd listener on the ltsp server that listens for connections from the thinclients. The thinclient uses nc to send the username to the ltsp server and it has to be of form guest-<hostname>.
inetd then runs a script that creates a user on the ltspserver the same way as lightdm does:
that script is still missing a check that the hostname actually exists before creating the user
Then there's an additional ltspguestsshd running that has a PAM stack that allows users to login without password.
ltspserver-guest-login checks that the username is of form guest-<remote hostname> and let's the user login if it matches:
If you run ssh with option -o NumberOfPasswordPrompts=0, it logs in without a password without using keys or anything else..
The code is not in actual use yet, so there are probably some issues still..
My ltsp servers are now pxe booting themselves using the same image as the clients, so the code has some quirks for that too..
vmlintu: cool! I don't know where in the logs you saw that, but for "real" guest logins here I'm just creating a local user and using an nbd swap mount from the server, formatted as ext4, for /home/guest...
I.e. there's no ssh/sshfs to the server involved at all
|16:54||Fenuks|2 has joined IRC (Fenuks|2!~Fenuks@220.127.116.11)|
alkisg1: that's for fatclients?
Yup, although for thin clients you'd need server-side users as you said, ok
yes, for fat clients I'm using pretty much the normal lightdm guest session like you do
Fat clients are much easier for guest logins.
On normal ltsp servers one can of course create the guest users once when setting it up
I haven't been following lately - is lightdm out of the picture now?
|17:09||freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Quit: So long and thanks for all the fish)|
vmlintu: I think we've decided that we don't want to rip out ldm and start clean with ltsp6, but to progressively implement stuff _before_ removing ldm, so that then replacing ldm with lightdm is a much smaller task than it is now
|17:15||GrembleBean has left IRC (GrembleBean!~Ben@cpc35-aztw23-2-0-cust207.18-1.cable.virginm.net, Quit: I Leave)|
|17:34||Fenuks|2 has left IRC (Fenuks|2!~Fenuks@18.104.22.168, Ping timeout: 245 seconds)|
|18:05||ogra_ has left IRC (email@example.com, Ping timeout: 264 seconds)|
|18:05||Fenuks has left IRC (Fenuks!~Fenuks@22.214.171.124, Quit: KVIrc 4.3.1 Aria http://www.kvirc.net/)|
|18:05||ogra_ has joined IRC (firstname.lastname@example.org)|
|18:10||ogra_ has left IRC (email@example.com, Max SendQ exceeded)|
|18:11||ogra_ has joined IRC (firstname.lastname@example.org)|
|18:16||vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)|
|18:21||alkisg is now known as work_alkisg|
|18:21||alkisg1 is now known as alkisg|
|18:47||workingcats has left IRC (email@example.com, Quit: Leaving)|
|18:59||kev_j has joined IRC (kev_j!~Kevin@web.ta-realty.com)|
|19:18||kev_j has left IRC (kev_j!~Kevin@web.ta-realty.com, Quit: Leaving)|
|19:46||ChadLepto has left IRC (ChadLepto!~chadlepto@unaffiliated/chadlepto, Ping timeout: 252 seconds)|
|20:41||monteslu has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
|20:45||monteslu has joined IRC (email@example.com)|
|21:19||alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)|
|21:42||36DABZBHP <36DABZBHPfirstname.lastname@example.org> has joined #ltsp|
|21:46||36DABZBHP <36DABZBHPemail@example.com> has quit IRC (K-Lined)|
|21:52||shawnp0wers has left IRC (shawnp0wers!~spowers@linuxjournal/staff/shawnp0wers, Remote host closed the connection)|
|21:57||shawnp0wers has joined IRC (shawnp0wers!~spowers@linuxjournal/staff/shawnp0wers)|
|22:01||vmlintu has left IRC (firstname.lastname@example.org, Ping timeout: 250 seconds)|
|22:07||brunolambert has left IRC (brunolambert!brunolambe@nat/revolutionlinux/x-dirbgtgicrovmwjn, Quit: Leaving.)|
anyone ever try something like profile-sync-daemon on a fat client setup?
I'm seeing tons of nfs writes all due to the browser profiles
I think if I can keep them local things'll be much more snappy
|22:32||hkfrvuwzbz has joined IRC (email@example.com)|
|22:35|||Paradox| has left IRC (|Paradoxfirstname.lastname@example.org, Ping timeout: 245 seconds)|
|22:36||hkfrvuwzbz is now known as |Paradox||
|22:49||Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)|
|23:43||freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)|