s3-winbindd and binding handles
Volker.Lendecke at SerNet.DE
Wed May 7 03:07:16 MDT 2014
On Wed, May 07, 2014 at 05:19:02PM +1200, Andrew Bartlett wrote:
> I've spent the day working on getting the source3 winbind to work like
> the source4 one, and one idea I've been wanting to understand the
> possibilities for is to use IRPC as a method to communicate to winbindd
> with (either directly calling the s4 irpc stack, or even better a merged
> stack based on the new s3 messaging code).
> I've started to understand how the winbindd_dual stuff works, and while
> the method for doing DCE/RPC on top of our winbindd pipe protocol is a
> bit odd, I really like the way we use the common dcerpc binding handle
> stuff on top of it.
> It even looks like it might be possible to have winbindd listen on irpc,
> and then forward that over the internal winbind pipe to the right target
> process, which would be pretty neat and avoid a pile of marshalling and
> It's been a long time since I've been seriously inside the guts of
> winbindd, and I'm intrigued with what has been done recently (and not so
> My current work in progress is here:
> My next goal is to have winbindd answer the SamLogon protocol the
> source4 auth system uses, and to extend that to include everything we
> need, particularly for the RODC.
To me this looks as if the parent winbind loops inside a
nested event context processing the irpc request. This would
block all other async requests that might be handled
concurrently. Am I getting this right?
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de
More information about the samba-technical