IRC chat logs for #ltsp on irc.libera.chat (webchat)


Channel log from 13 January 2022   (all times are UTC)

02:27vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b, Quit: leaving)
03:38vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)
04:26vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving)
07:05woernie has joined IRC (woernie!~werner@p5ddec734.dip0.t-ipconnect.de)
07:05woernie_ has left IRC (woernie_!~werner@p5b296789.dip0.t-ipconnect.de, Ping timeout: 256 seconds)
07:10ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:17
<sunweaver>
alkisg: thanks (about case in ltsp.ipxe). Thought so.
07:18
<alkisg>
I've started working on epoptes first, as it had a regression; in a few days I'll finish with it and start working on the new ltsp release
11:15fiesh_ is now known as fiesh
11:23
<sunweaver>
alkisg: great.
12:00lucascastro has left IRC (lucascastro!~lucascast@192-140-51-251.static.oncabo.net.br, Remote host closed the connection)
12:09lucascastro has joined IRC (lucascastro!~lucascast@192-140-51-251.static.oncabo.net.br)
12:51danboid has joined IRC (danboid!~dan@portal.salford.ac.uk)
12:52
<danboid>
I'm trying to troubleshoot my PAM/SSH issues but can't access the logs on the LTSP clients. How do I create a local sudo user that is enabled in the LTSP image?
12:53
I already have such a user in the source VM image but I presume LTSP disables thej by default
12:55
Also, although I've disabled the lightdm option to show the users on the login screen and that option works in my source VM image, I still see all the users when I boot the same image under LTSP
12:56
Its as if its not reading the lightdm config file under LTSP and no, I've not got any snapshots now
12:57
The same image after being compressed by ltsp image that is
13:15
It looks like I might do this using the PASSWORDS statement in ltsp.conf, maybe but the man page doesn't mention sudo
13:16
Does LTSP expect that these users already exist in the image so if they do exist and are in the sudo group and are mentioned in the PASSWORDS statement I'll be able to log in as a sudo user?#
13:39
Although thats not quite what I want as I don't want anyone to be able top login as a sudo user
13:39
Is there not some user whitelist or something?
13:40
It seems LTSP disables local users in the source image right?
13:42
Someone other than alkisg must know the answer to this
13:47
Actually no, the ltsp.conf man page says
13:47
"Normally, all the server users are listed on the client login screens and are permitted to log in"
13:48
Thats not been my experience. I have not been able to login as any of the users the exist on the image
14:02
The PWMERGE_SUR=, PWMERGE_SGR=, PWMERGE_DGR=, PWMERGE_DUR= commands hint at why I'm still seeing all the local users listed on the lightdm login screen
14:11
I've read the pwmerge comments / instructions but I don't understand them. I'm not sure what the difference is between the the destination and the merged accounts
14:12
Are the merged passwords the destination?
14:12
*Aren't?
14:40woernie has left IRC (woernie!~werner@p5ddec734.dip0.t-ipconnect.de, Ping timeout: 256 seconds)
14:40woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de)
14:53
<alkisg>
danboid: see the last line in https://ltsp.org/man/ltsp.conf/
14:54
You'll get root that way, then you'll be able to troubleshoot
14:54
Although it's much easier to just use epoptes and right click > open a root terminal
15:02
After you get root, you can add temporary sudo users with `adduser`, if you want to test PAM with them
15:13
<danboid>
alkisg, Ill try that. What about pwmerge vs lightdm?
15:14
alkisg, In my lightdm.conf I have the lines
15:14
[SeatDefaults]
15:14
greeter-hide-users=true
15:15
but that seems to be overridden by ltsp / pwmerge
15:32
<alkisg>
See LIGHTDM_CONF in ltsp.conf
15:32
You can specify things from there if you can't do it via your image
15:34
pwmerge shouldn't be needed since you shouldn't be using accounts from the image anyway
16:45woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 250 seconds)
16:45woernie has joined IRC (woernie!~werner@p5ddec734.dip0.t-ipconnect.de)
16:55
<danboid>
alkisg, LIGHTDM_CONF goes under the [clients] section of ltsp.conf right?
16:56
<alkisg>
Yup
18:39vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)
19:31dan_ has joined IRC (dan_!~dan@portal.salford.ac.uk)
19:31danboid has left IRC (danboid!~dan@portal.salford.ac.uk, Read error: Connection reset by peer)
19:52dan_ has left IRC (dan_!~dan@portal.salford.ac.uk, Quit: Leaving)
20:16
<alkisg>
Ouch, now I remember, there was NO `cp -u` in older busybox versions
20:23
<vagrantc>
also very dependent on a working clock ... sometimes the clock doesn't get updated till after initramfs ...
20:23
but maybe that's just the buggy systems i work with...
20:38
<alkisg>
It was added in 2016 in busybox, so only older distributions are affected; a cp -au || cp -a should be good enough then :)
20:45
sunweaver, vagrantc : https://github.com/ltsp/ltsp/issues/636#issuecomment-1012501601
21:06ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)