05:34 | DeluxeSk8rBird has joined IRC (DeluxeSk8rBird!~DeluxeSk8@27.125.241.140) | |
05:40 | DeluxeSk8rBird1 has joined IRC (DeluxeSk8rBird1!~DeluxeSk8@27.125.241.140) | |
05:42 | DeluxeSk8rBird has left IRC (DeluxeSk8rBird!~DeluxeSk8@27.125.241.140, Ping timeout: 240 seconds) | |
06:03 | DeluxeSk8rBird1 has left IRC (DeluxeSk8rBird1!~DeluxeSk8@27.125.241.140, Quit: Leaving) | |
06:03 | DeluxeSk8rBird has joined IRC (DeluxeSk8rBird!~DeluxeSk8@27.125.241.140) | |
07:10 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
07:47 | DeluxeSk8rBird has left IRC (DeluxeSk8rBird!~DeluxeSk8@27.125.241.140, Ping timeout: 250 seconds) | |
07:57 | DeluxeSk8rBird has joined IRC (DeluxeSk8rBird!~DeluxeSk8@27.125.241.163) | |
08:01 | DeluxeSk8rBird1 has joined IRC (DeluxeSk8rBird1!~DeluxeSk8@27.125.241.163) | |
08:04 | DeluxeSk8rBird has left IRC (DeluxeSk8rBird!~DeluxeSk8@27.125.241.163, Ping timeout: 256 seconds) | |
09:03 | woernie has left IRC (woernie!~werner@p5ddec734.dip0.t-ipconnect.de, Ping timeout: 256 seconds) | |
09:03 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
09:34 | DeluxeSk8rBird1 has left IRC (DeluxeSk8rBird1!~DeluxeSk8@27.125.241.163, Ping timeout: 256 seconds) | |
09:38 | DeluxeSk8rBird1 has joined IRC (DeluxeSk8rBird1!~DeluxeSk8@27.125.241.163) | |
09:51 | DeluxeSk8rBird1 has left IRC (DeluxeSk8rBird1!~DeluxeSk8@27.125.241.163, Remote host closed the connection) | |
09:51 | DeluxeSk8rBird1 has joined IRC (DeluxeSk8rBird1!~DeluxeSk8@27.125.241.163) | |
09:59 | DeluxeSk8rBird1 has left IRC (DeluxeSk8rBird1!~DeluxeSk8@27.125.241.163, Ping timeout: 256 seconds) | |
10:17 | bcg_ has left IRC (bcg_!~b@213-216-205-19.co.dnainternet.fi, Quit: bcg_) | |
10:34 | bcg has joined IRC (bcg!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi) | |
12:33 | lucascastro has left IRC (lucascastro!~lucascast@192-140-51-251.static.oncabo.net.br, Remote host closed the connection) | |
12:38 | lucascastro has joined IRC (lucascastro!~lucascast@192-140-51-251.static.oncabo.net.br) | |
12:41 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 256 seconds) | |
12:41 | woernie has joined IRC (woernie!~werner@p5ddec734.dip0.t-ipconnect.de) | |
14:07 | danboid has joined IRC (danboid!~dan@portal.salford.ac.uk) | |
14:10 | <danboid> alkisg, I'm back to investigating why LTSP doesn't like nslcd for LDAP. There are two oddities with LTSP/nslcd. The first is that when I run `su - LDAPUSER` on a LTSP client it logs me straight in instead of asking for a password like I'd expect but
| |
14:11 | alkisg, When I run `getent passwd LDAPUSER` on the LTSP client I get incorrect info but the same nslcd config gives me correct info when not using LTSP
| |
14:12 | Most notably the UID and GID are incorrect, as is my full user name
| |
14:14 | The UID and GID are incorret when I run `getent passwd LDAPUSER` under LTSP+nslcd but they are correct when I run Ubuntu 20.04 + nslcd w/o LTSP
| |
14:15 | Could this be because LTSP uses a different PAM library to LTSP?
| |
14:16 | nslcd uses a different PAM library vs LTSP?
| |
14:16 | alkisg, nsld uses libpam-ldapd
| |
14:18 | mistertwister has joined IRC (mistertwister!~mistertwi@business-178-015-081-022.static.arcor-ip.net) | |
14:18 | <danboid> I tried tried on rsyslog debugging for PAM but the rsyslog debug logs were huge and I wasn't finidig anythig to dio with PAM
| |
14:19 | plus, they only worked in my VM and not on the LTSP client for some reasin
| |
14:19 | mistertwister has left IRC (mistertwister!~mistertwi@business-178-015-081-022.static.arcor-ip.net, Client Quit) | |
14:20 | <danboid> It seems to me that my nslcd config is fine but its clashing with something in LTSP
| |
14:20 | or LTSP expects PAM to be handled differently?
| |
14:26 | I don't know if its relevant to LTSP but by browsing packages.ubuntu.com I can see sssd-ldap depends upon sssd-common whic in turn depends upon libpam0g, which is obviously not the same as libpam-ldapd as used by nslcd
| |
14:28 | I think most of LTSP is shell scripts so I'm not sure this matters?
| |
14:50 | ogra` is now known as ogra | |
15:04 | <alkisg> danboid: I think it would be much easier for you to hire someone to solve these issues in a couple of hours instead of trying for weeks :)
| |
15:04 | I don't think that issue is related to the LTSP code. No, LTSP doesn't use any different PAM libraries...
| |
16:04 | <danboid> I don't want to give up just yet! No-one is shouting at me yet :)
| |
16:05 | Looking at /usr/share/pam-configs/ltsp opn the client I can see its using Additional mode without me specifying it ltsp.conf, which is prob what it should be doing
| |
16:06 | <alkisg> Additional is correct for your use case, as you don't want LTSP to do the authentication, you just want it to do the sshfs mount
| |
17:54 | <danboid> alkisg, /run/ltsp/pam/LDAPUSER/shadow doesn't look right on my LTSP client/ The second field contains pamltsp. I'd expect this field to be a hash of the users password, if its used conventionally
| |
17:54 | dan_ has joined IRC (dan_!~dan@portal.salford.ac.uk) | |
17:59 | danboid has left IRC (danboid!~dan@portal.salford.ac.uk, Ping timeout: 256 seconds) | |
18:02 | danboid has joined IRC (danboid!~dan@portal.salford.ac.uk) | |
18:06 | dan_ has left IRC (dan_!~dan@portal.salford.ac.uk, Ping timeout: 256 seconds) | |
19:47 | danboid has left IRC (danboid!~dan@portal.salford.ac.uk, Quit: Leaving) | |
21:36 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e) | |
21:43 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
21:44 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving) | |
21:57 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b) | |
22:48 | lucascastro has left IRC (lucascastro!~lucascast@192-140-51-251.static.oncabo.net.br, Ping timeout: 256 seconds) | |