Hi dave
I have found the following items in the htmldocs:
The pam_winbind module in the 2.2.2 release only supports the auth and
account module-types. The latter simply performs a getpwnam() to verify
that the system can obtain a uid for the user. If the libnss_winbind
library has been
Hi giuseppe
after some more investigation ive found the following sequence to be
100% repeatable.
2 users, dave elina. dave has a local account, elina does not. After
reboot or restart of the winbindd daemon, dave can login but elina can
not. After logging in as dave, wbinfo -n dave returns
I cant get a login from an FC3 setup unless the user has a local account.
Jun 10 11:53:12 fc3 login(pam_unix)[12082]: check pass; user (elina) unknown
Jun 10 11:53:12 fc3 login(pam_unix)[12082]: authentication failure;
logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost= user=elina
Jun 10
Hi Giuseppe
I was thinking that getpwnam should fail, that user doesnt exist locally.
But the pam_unix and/or pam stack should be able to cope with that ?
dave
giuseppe59 wrote:
Hello David
I experience the same problem.
wbinfo -u, wbinfo -g, wbinfo -t, getent passwd,
kinit, kpassw work
David Rigler wrote:
Hi Giuseppe
I was thinking that getpwnam should fail, that user doesnt exist locally.
But the pam_unix and/or pam stack should be able to cope with that ?
dave
Hi dave
Yes, they should be able.
I have written a simple C program which is calling getpwnam. If passwd
