It is the first time I play with gdm (die-hard KDE user, but the customer is king ...)
It looks like an 'issue' between pam/gdm/NDS (Novell) If I made locally a user Test1 Than I get this in log/messages : Apr 1 11:07:18 linuxtse gdm(pam_unix)[2520]: check pass; user unknown Apr 1 11:07:18 linuxtse gdm(pam_unix)[2520]: authentication failure; logname= uid=0 euid=0 tty=192.168.10.253:0 ruser= rhost=192.168.10.253 If I remove that user again I get this : Apr 1 11:07:18 linuxtse gdm(pam_unix)[2520]: could not identify user (from getpwnam(Test1)) Apr 1 11:07:18 linuxtse gdm-binary[2520]: Couldn't set acct. mgmt for Test1 Now my Q is why is it using pam_unix and not the ncp stuff... or is it not.... confused 100% in secure log I see this, clearly using the NSD and all is well, Apr 1 11:12:45 linuxtse pam_ncp_auth[2520]: using server LTSPTEST ctxs CC group (null) Apr 1 11:12:45 linuxtse pam_ncp_auth[2520]: nw_create_verify_conn_to_tree: trying to resolve Test1.CC Apr 1 11:12:45 linuxtse pam_ncp_auth[2520]: trying to login as Test1.CC Apr 1 11:12:46 linuxtse pam_ncp_auth[2520]: User Test1.CC was successfully authorized by NDS server LTSPTEST on tree LINUX_TREE Apr 1 11:12:46 linuxtse pam_ncp_auth[2520]: Auth OK Apr 1 11:12:46 linuxtse pam_ncp_auth[2520]: start of nw_auto_mount_home Apr 1 11:12:46 linuxtse pam_ncp_auth[2520]: saving user_info Apr 1 11:12:46 linuxtse pam_ncp_auth[2520]: final PAM retval 0 Or is there still something wacky in the /etc/pam.d/gdm file? auth requisite pam_nologin.so auth sufficient pam_unix.so nullok auth sufficient /lib/security/pam_ncp_auth.so -zAX -n -A -d -l -u,,,gcds ndsserver=LTSPTEST:CC auth required pam_deny.so account required pam_unix.so session required pam_unix.so session optional /lib/security/pam_ncp_auth.so password required pam_unix.so nullok obscure min=4 I noticed indeed that a change to this file not always get picked up by pam. It seems to help to add/remove a line (of comments) Than pam 'sees' the change right away Just an edit in on of the line leaving the number of lines in the config file as is gives that 'waiting' behaviour... strange. Peter -----Original Message----- From: s. keeling [mailto:[EMAIL PROTECTED] Sent: Thu 4/1/2004 10:52 AM To: [EMAIL PROTECTED] Cc: Subject: Re: [clug-talk] PAM & GDM Incoming from Peter Van den Wildenbergh: > > I still cannot get passed the Gnome login screen (GDM) > There I get a "Incorrect username or password". fwiw, I've run into that before. I ran passwd from a terminal, logged out and tried to log back in via gdm, and gdm refused to recognise the change. The old password was still in effect! I can't remember if simply waiting, or a re-boot, was required for gdm to pick up on it. It eventually did within a day (and figuring out that it finally had was no fun either). "dpkg -r [gkx]dm"! -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - - _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
<<winmail.dat>>
_______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
