AuthTimeoutError with PAM-enabled su about neatx

[GoogleCodeExporter]

Ok, as far as i can tell, here's what's happening:

Aug 27 15:07:48 enterprise nxserver-login[17424]: DEBUG auth:50
Authenticating as 'bernard', running ['/usr/lib64/neatx/nxserver',
'--proto=3030000', '--', 'bernard']
Aug 27 15:07:48 enterprise nxserver-login[17424]: DEBUG auth:53 Auth
command ['/usr/lib64/neatx/ttysetup', '/bin/su', 'bernard', '-c', 'cd &&
/usr/lib64/neatx/nxserver --proto=3030000 -- bernard']
Aug 27 15:07:48 enterprise su[17426]: Successful su for bernard by nx
Aug 27 15:07:48 enterprise su[17426]: + /dev/pts/0 nx:bernard
Aug 27 15:07:48 enterprise su[17426]: pam_unix(su:session): session opened
for user bernard by (uid=110)
Aug 27 15:08:18 enterprise nxserver-login[17424]: DEBUG auth:109
Authentication timed out (output='Password: ')

su is being run, and it's immediately succeeding, without prompting for a 
password.
I'm guessing your pam setup is configured to allow this. I think the fix is to 
change
lib/auth.py so that this is allowed for.

Original comment by kormat on 30 Aug 2009 at 1:25

• Changed state: Accepted

[GoogleCodeExporter]

Sorry, i'm wrong. su is outputing a password prompt (as the 'Authentication 
timed
out' log entry shows). And su is succeeding (as the su log entries show). 
However the
nxserver command isn't getting run. Can you tell me what happens if you run 
this by
hand, as the nx user:

/bin/su bernard -c 'cd && /usr/lib64/neatx/nxserver --proto=3030000 -- bernard'

Thanks,
Steve

Original comment by kormat on 30 Aug 2009 at 1:32

[GoogleCodeExporter]

Manually running it is ok:

enterprise ~ # su - nx -s /bin/bash
nx@enterprise ~ $ /bin/su bernard -c 'cd && /usr/lib64/neatx/nxserver 
--proto=3030000
-- bernard'
Password: 
NX> 103 Welcome to: enterprise.cafarelli.fr user: bernard
NX> 105 

And the corresponding log:
Aug 30 20:21:42 enterprise su[9791]: Successful su for nx by root
Aug 30 20:21:42 enterprise su[9791]: + /dev/pts/4 root:nx
Aug 30 20:21:42 enterprise su[9791]: pam_unix(su:session): session opened for 
user nx
by bernard(uid=0)
Aug 30 20:21:46 enterprise su[9820]: Successful su for bernard by nx
Aug 30 20:21:46 enterprise su[9820]: + /dev/pts/4 nx:bernard
Aug 30 20:21:46 enterprise su[9820]: pam_unix(su:session): session opened for 
user
bernard by bernard(uid=110)
Aug 30 20:22:07 enterprise nxserver[9822]: INFO nxserver:689 Starting nxserver 
for
user bernard
Aug 30 20:22:07 enterprise nxserver[9822]: DEBUG protocol:172 >>> 'NX> 103 
Welcome
to: enterprise.cafarelli.fr user: bernard\n'
Aug 30 20:22:07 enterprise nxserver[9822]: DEBUG protocol:172 >>> 'NX> 105 '

I've tried setting /bin/sh as login shell, run ssh nx@enterprise and nxserver, 
same
behaviour

Original comment by [email protected] on 30 Aug 2009 at 6:50

[GoogleCodeExporter]

Hmm. There seems to be quite a long pause between su suceeding, and nxserver 
being run: 

Aug 30 20:21:46 enterprise su[9820]: pam_unix(su:session): session opened for 
user
bernard by bernard(uid=110)
Aug 30 20:22:07 enterprise nxserver[9822]: INFO nxserver:689 Starting nxserver 
for
user bernard

It's possible that nxserver-login's timeout is too short. If you try increasing 
it
from 30 to 60 on this line:
http://code.google.com/p/neatx/source/browse/trunk/neatx/lib/auth.py#71 , that 
might
fix things. Let me know.

Original comment by kormat on 8 Sep 2009 at 5:40

[GoogleCodeExporter]

Thanks to your comment, I have solved this one! Commenting on the long delay 
between
su and nxserver, I saw nxssh was waiting (and timeouting) on getting xauth 
lock...

The bug was in the ebuild, which installs ~nx owned by root:root, thus 
preventing nx
user from creating .Xauthority (not sure how disabling PAM helped for this one, 
but
oh well...)

Now it works, and the authentication/login part is as fast as nx free edition at
least :) Thanks a lot for your help!

Original comment by [email protected] on 8 Sep 2009 at 10:15

[GoogleCodeExporter]

Great, glad to hear it's solved.

Original comment by kormat on 14 Sep 2009 at 5:18

• Changed state: Fixed