Backporting DCERPC Security Context Multiplexing?

[Stefan Metzmacher]

Hi,

>> Here's what I'm going with. No real changes, just the
>> comments/commit massage updates and talloc -> talloc_zero change.
>>
>> RB+.
>>
>> Phew. That was a marathon review session :-).

As these patches would like fix real world problems, see:

https://bugzilla.samba.org/show_bug.cgi?id=7113
https://bugzilla.samba.org/show_bug.cgi?id=11892

I'm wondering if we should backport them to current releases?
We could also turn the feature off in order to keep the old
behavior.

The patchset has a lot of patches, but the changes are very isolated
in the core s4:rpc_server and we have an it's tested a lot in
raw_protocol.py. I have a 4.9 backport here:

https://git.samba.org/?p=metze/samba/wip.git;a=shortlog;h=refs/heads/v4-9-dcerpc-auth

And a pipeline is running here:
https://gitlab.com/samba-team/devel/samba/pipelines/43756435

What do you think?

metze

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20190117/4d26d572/signature.sig>