[proof of concept] libwbclient.so

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Guenther,

> Gerald (Jerry) Carter wrote:
>> Volker,
> 
>>> One main question for me is: How much of the winbind pipe do
>>> we want to expose via an API that we stick to in the future?
>>> For example, what about the DC lookup routines that gd has
>>> added recently for his krb5 locator plugin? How do we handle
>>> changes here?
>> My goal is that this library should be the only way
>> that smbd communicates with winbindd.  So therefore if a
>> fucntion is necessary added smbd, it must be added to the
>> library.  I want to remove all compile time static links
>> between smbd and winbindd.
> 
> For this purpose I fully agree with your approach.
> 
> As long as you preserve a way to access the "good" old 
> API for richer commands like PAM and others.

Seem my additional comments to Volker.  I think the library
should expose all operations in the winbindd pipe protocol
and that pam_winbindd and libnss_winbind should link again
libwbclient.so.

I'll finish fillout out the library today and tomorrow.
Also, this is our chance to remove unnecessary or
outdated calls if we want.



cheers, jerry
=====================================================================
Samba                                    ------- http://www.samba.org
Centeris                         -----------  http://www.centeris.com
"What man is a man who does not make the world better?"      --Balian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG1uYpIR7qMdg1EfYRAnu0AKDIimuVF43753XTQD7DCbRUeNbE3ACfZj2m
1qnyBFHQbFjTZaPTDRPc1Mw=
=YNKZ
-----END PGP SIGNATURE-----