Samba 4 and winbind

Alexander Bokovoy ab at
Mon Apr 15 11:23:29 MDT 2013

On Mon, Apr 15, 2013 at 7:12 PM, Rowland Penny <repenny at> wrote:

> On 15/04/13 16:47, Jeremy Allison wrote:
>> On Mon, Apr 15, 2013 at 04:42:50PM +0100, Rowland Penny wrote:
>>> Again, this I understand, but if Winbind was a stand alone daemon,
>>> like it is with S3, then you could choose to use it or not. I
>>> actually think that if there was a choice then most people would
>>> choose not to use winbind due to its complexity  and inconsistency.
>> Oh, bitching on winbindd again. Very popular on this list it
>> seems :-).
>> If you have specific problems, please log bugs. Don't just
>> try and make some specific code into the boogyman, we've
>> had enough of proprietarty vendors doing that against the
>> whole of Samba thanks very much, we don't need our own users
>> to join in.
>> Jeremy.
>>  OK, do you really want me to log a bug that basically says that because
> S3 & S4 winbinds are different and the fact that you cannot get the same
> uidNumber on the server as on the clients that winbind is broken!!
Yes, I do want you to log this bug. There is no reason why winbind
implementation in Samba AD DC should use unpredictable and dependent on the
order of allocations high watermark algorithm.

> You didn't answer the question either, why is winbind built into the
> samba4 samba daemon.
Design decision which has nothing to do with functionality exposed. Whether
it is built in or separate is irrelevant here, what is relevant is its ID
mapping algorithm being different from all already deployed in the wild by
means of previous Samba versions.

Please try to keep technical discussion to the point rather than driving it
/ Alexander Bokovoy

More information about the samba-technical mailing list