If you look at the source for these applications, you'll see that they contains a pam_start() function call. The service name argument must correspond to a file /etc/pam.d/<service-name>. If no such file exists you will default to using the 'other' service, which defaults to deny access. I suspect a lack of the appropriate file[s] is your problem. Cheers Andrew Mr E_T wrote: > > I have just compiled and installed linux-pam 0.75 and am having trouble > getting it to work. > > When I run the example programs - I get > > # > #blank > ... > ==> called pam_putenv() > got: `Success' > a test: c=[gamma], j=[mu] > Who are you? root > ==> called pam_authenticate() > got: `Authentication failure' > ./blank: invalid request > ==> called pam_end() > got: `Success' > > # > #check_user > Not Authenticated > > # > #xsh > ==> called pam_start() > got: `Success' > Who are you? root > ==> called pam_authenticate() > got: `Authentication failure' > ./xsh: invalid request > ==> called pam_end() > got: `Success' > > I have the shadow password suite installed already on my system but it > would appear that it is not being used. > > my messages log file contains - > Jan 1 10:52:36 mobius PAM-warn[1257]: service: blank [on terminal: <unknown>] > Jan 1 10:52:38 mobius PAM-warn[1257]: user: (uid=0) -> rot [remote: ?nobody@?nowhere] > Jan 1 10:52:44 mobius PAM-warn[1259]: service: check [on terminal: <unknown>] > Jan 1 10:52:44 mobius PAM-warn[1259]: user: (uid=0) -> nobody [remote: ?nobody@?nowhere] > Jan 1 10:52:47 mobius PAM-warn[1262]: service: xsh [on terminal: <unknown>] > Jan 1 10:52:49 mobius PAM-warn[1262]: user: (uid=0) -> root [remote: ?nobody@?nowhere] > > This is the same from both a remote login and a console login - I am not > sure hwere this is starting? > > -- > regs MR E_T > > _______________________ > \ \ > \ OOHH I hate TYPOS \ > \ \ > ~~~~~~~~~~~~~~~~~~~~~~~ > > _______________________________________________ > > Pam-list@redhat.com > https://listman.redhat.com/mailman/listinfo/pam-list
