IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 28 September 2018 (all times are UTC)
| 00:09 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 01:28 | chksome has joined IRC (chksome!~chksome@cpe-74-140-207-12.cinci.res.rr.com) | |
| 01:34 | chksome has left IRC (chksome!~chksome@cpe-74-140-207-12.cinci.res.rr.com, Quit: Textual IRC Client: www.textualapp.com) | |
| 01:36 | chksome has joined IRC (chksome!~chksome@cpe-74-140-207-12.cinci.res.rr.com) | |
| 02:26 | chksome has left IRC (chksome!~chksome@cpe-74-140-207-12.cinci.res.rr.com, Quit: My MacBook has gone to sleep. ZZZzzz…) | |
| 05:52 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 08:39 | Natureshadow has joined IRC (Natureshadow!45d1515d22@commu.teckids.org) | |
| 09:41 | laserman has joined IRC (laserman!~mherweg@193.77.13.202) | |
| 09:53 | laserman has left IRC (laserman!~mherweg@193.77.13.202, Ping timeout: 252 seconds) | |
| 11:13 | GodFather has joined IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net) | |
| 11:47 | GodFather has left IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net, Ping timeout: 245 seconds) | |
| 11:58 | GodFather has joined IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net) | |
| 12:12 | GodFather has left IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net, Ping timeout: 252 seconds) | |
| 12:33 | Faith has joined IRC (Faith!~Paty_@unaffiliated/faith) | |
| 12:52 | GodFather has joined IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net) | |
| 13:10 | GodFather has left IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net, Ping timeout: 268 seconds) | |
| 13:42 | GodFather has joined IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net) | |
| 13:49 | GodFather has left IRC (GodFather!~rcc@174-081-217-069.dhcp.chtrptr.net, Ping timeout: 252 seconds) | |
| 13:50 | lucascastro has left IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br, Remote host closed the connection) | |
| 15:48 | alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Ping timeout: 252 seconds) | |
| 16:06 | lucascastro has joined IRC (lucascastro!~lucascast@177-185-139-186.isotelco.net.br) | |
| 17:49 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 18:00 | ricotz_ has joined IRC (ricotz_!~ricotz@ubuntu/member/ricotz) | |
| 18:02 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Ping timeout: 246 seconds) | |
| 19:19 | carbm2 has joined IRC (carbm2!42cc1464@gateway/web/freenode/ip.66.204.20.100) | |
| 19:23 | <carbm2> I'm in the process of setting up an ltsp server for a classroom. I'm using Ubuntu Mate 16.04, Power Broker Identity Services for AD auth, and I'm trying to use Local Apps. The problem I'm having is we create groups in AD that are based on student schedules. These group names are often long. The problem I have is that any student who is in a group that has a name longer than 30 characters will fail to get created on the client for loca
| |
| 19:31 | <vagrantc> i don't think there's any specific limitation that LTSP places on the group names...
| |
| 19:31 | <carbm2> I've looked for a way to skip groups that exceed a certain length but I haven't been successful in modifying X01-localapps.
| |
| 19:32 | <vagrantc> what version of ltsp are you running?
| |
| 19:33 | there have been a few changes to some of that code since 16.04, and 16.04 was quite outdated at the time of release anyways
| |
| 19:33 | <carbm2> ltsp-server-standalone 5.5.7-1ubuntu1
| |
| 19:34 | <vagrantc> can you share one of these example group names?
| |
| 19:35 | <carbm2> Group[14 of 14] name = is-teachername-9-socialstudies-504 (gid = 1535147446)
| |
| 19:36 | <vagrantc> ok, the fixes since 5.5.7 aren't likely to change much
| |
| 19:36 | <carbm2> The moment I remove the user from that group the auth.log shows the useradd command and adding the user to the groups.
| |
| 19:37 | <vagrantc> can you manually add the group with groupadd?
| |
| 19:38 | groupadd is-teachername-9-socialstudies-504
| |
| 19:38 | groupadd: 'is-teachername-9-socialstudies-504' is not a valid group name
| |
| 19:38 | there's basically no way to fix it
| |
| 19:39 | ignoring groups would also be ... problematic
| |
| 19:39 | <carbm2> I would expect in the X01-localapps to be able to trim the name down to 30 characters. As long as the GUIDs matched I should still be able to set permissions if needed.
| |
| 19:40 | I've tried replacing $gr_name with ${gr_name:0:30} and I've been unsuccessful in getting a working solution. All logins break with the changes I've tried.
| |
| 19:40 | <vagrantc> other than mangling the group name ... which might be possible
| |
| 19:40 | but then you'd end up with is-teachername-9-socialstudies-50 be assigned the same name with two different gids
| |
| 19:41 | <carbm2> Since this problem only affects the ltsp client that would not be an issue for me.
| |
| 19:41 | <vagrantc> you don't actually use these groups from the client?
| |
| 19:42 | and it wouldn't give some users access to the wrong files?
| |
| 19:42 | <carbm2> Not on the client.
| |
| 19:45 | <vagrantc> gr_name=$(echo $gr_name | cut -b 1-30)
| |
| 19:45 | might be a more elegant way to handle it
| |
| 19:48 | alternately, if [ "${#gr_name}" -le 30 ]; then #do the usual things ; fi
| |
| 19:48 | that would skip creating the group at all
| |
| 19:49 | if they truely don't need the group
| |
| 19:50 | <carbm2> I would be completely ok with skipping them all together as they are invalid. Let me try that.
| |
| 19:51 | <vagrantc> not sure what a valid solution for fixing this upstream would be ...
| |
| 19:53 | i guess we could use the same approach as for invalid characters ...
| |
| 19:54 | which is a horrible, ugly hack
| |
| 19:54 | :)
| |
| 19:56 | although apparently, since the gid is so large, that would also trigger the issue
| |
| 19:57 | as it creates a temporary group of ltsp_temporary_group_1535147446
| |
| 19:59 | huh ... doesn't appear to be a problem with that group, though
| |
| 20:00 | but it's definitely over the 30 characters
| |
| 20:00 | <carbm2> I don't have a problem with my other groups that have long names like that. I'm going to check the - vs _.
| |
| 20:00 | <vagrantc> carbm2: this seems worth filing a bug report, especially if you can test it on a newer version
| |
| 20:01 | carbm2: does your version have the is_valid_name function?
| |
| 20:01 | <carbm2> changing it to _ didn't change anything.
| |
| 20:01 | Yes it does.
| |
| 20:02 | <vagrantc> for some bizarre reason, though, groupadd ltsp_temporary_group_1535147446 works fine, even though it's 31 characters
| |
| 20:03 | <carbm2> I'm betting the hard limit is actually 32.
| |
| 20:03 | Looks like I can create a group as long as 31 but not 32.
| |
| 20:04 | <vagrantc> yup
| |
| 20:04 | similar behavior on debian stretch and groupadd
| |
| 20:07 | <carbm2> The if [ ${#gr_name} -le 31 ]; then works fine when wrapped around the group list block.
| |
| 20:08 | <vagrantc> we could update is_valid_name to include length requirements, and as long as the uid/gid don't extend past 32, it should work fine
| |
| 20:08 | i was able to create one with 32 characters
| |
| 20:08 | unless wc was counting the newline
| |
| 20:09 | ah, you're right, it's 32
| |
| 20:09 | -lt 32
| |
| 20:10 | so, the real question is ... where does the 31-character limit come from, and is that universal? then we could fix it upstream ... otherwise ... hrm.
| |
| 20:10 | carbm2: please file a bug about it in launchpad!
| |
| 20:10 | <carbm2> With a little google fu it appears that it definitely is a linux hard limit.
| |
| 20:11 | <vagrantc> granted, the real fix is to just support pam properly ... the localapps/remoteapps stuff is really quite hackish
| |
| 20:11 | <Hyperbyte> Isn't this a kernel limitation?
| |
| 20:12 | <carbm2> Report the bug here: https://bugs.launchpad.net/ltsp ?
| |
| 20:12 | <Hyperbyte> Or PAM or whatever.
| |
| 20:16 | <vagrantc> carbm2: sure
| |
| 20:16 | Hyperbyte: might be ...
| |
| 20:21 | <carbm2> vagrantc: Thank you! I have a working solution now.
| |
| 20:35 | <vagrantc> carbm2: added a one-line patch that might fix the issue
| |
| 20:40 | Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving) | |
| 20:51 | ricotz_ has left IRC (ricotz_!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 20:52 | <carbm2> Can confirm your patch works.
| |
| 20:53 | <vagrantc> now i just need to confirm it doesn't break anything on my own setups :)
| |
| 20:54 | hope to include it in a release in the next month or so
| |
| 21:11 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 22:14 | adrianorg has left IRC (adrianorg!~adrianorg@179.177.214.91.dynamic.adsl.gvt.net.br, Ping timeout: 264 seconds) | |
| 22:17 | adrianorg has joined IRC (adrianorg!~adrianorg@179.177.214.91.dynamic.adsl.gvt.net.br) | |
| 22:27 | Helenah has left IRC (Helenah!~s98259@unaffiliated/iveeee, Ping timeout: 245 seconds) | |