pam_winbind.so modules

[Esh, Andrew]

Those are the same two warnings I always get, so you're doing it right.

BTW: Your comments about pam being optional are correct. I got the idea from
the documentation that it was required, but then I noticed winbindd and
Samba user authentication both still worked without it. Now I don't use it
at all. All it does is allow Windows users to make use of Unix services
which require authentication, like telnet and FTP.

-----Original Message-----
From: Rafal Szczesniak [mailto:mimir at spin.ict.pwr.wroc.pl]
Sent: Saturday, September 29, 2001 7:45 PM
To: Tim Potter
Cc: samba-technical at lists.samba.org
Subject: Re: pam_winbind.so modules


On Sun, 30 Sep 2001, Tim Potter wrote:

> Rafal Szczesniak writes:
>
> > All right. I've looked around and noticed that --with-pam (and pam
> > developer's files) are needed. Using --with-pam option results in
> > a lot of compile errors in nsswitch/pam_winbind.c
> > In that case, I think it should be pointed explicitly in
> > documentation (i.e. man page) that utilising pam module is _optional_
>
> It compiles fine for me.  What errors do you get?

Sorry for false alarm. I did not had developer's files for libpam
(libpam0g-dev package in debian) and when I got it, I forgot to
recompile everything again. Now, I've compiled with 2 warnings (for
winbindd):

nsswitch/winbind_pam.c:30 warning: static declaration for
'parse_domain_user' follows non-static
nsswitch/winbind_pam.c:35 warning: static declaration for
'trust_keystr' follows non-static

Beside that, compilation of winbind were nice-n-easy.

> Tim.

once again, sorry for false alarm
everything seems to be ok, now

Rafal 'Mimir' Szczesniak <mimir at spin.ict.pwr.wroc.pl>   |
*BSD, Linux and Samba                                  /
______________________________________________________/

-------------- next part --------------
HTML attachment scrubbed and removed