[PATCH] lib/param: Consolidate code to enable smb signing on the server, always enable on AD DC

Andrew Bartlett abartlet at samba.org
Sun Apr 6 17:11:10 MDT 2014

On Fri, 2013-11-22 at 13:24 +0100, David Disseldorp wrote:
> On Fri, 22 Nov 2013 14:43:34 +1300
> Andrew Bartlett <abartlet at samba.org> wrote:
> > I tried an autobuild with another patch, and that passed.  So I tried with just
> > this patch, and that autobuild passed too, which doesn't provide me with any more insights
> > on this.  
> > 
> > Do you think we should dare to try an official autobuild again?
> I pushed again. It made it through this time.
> Cheers, David

I'm wondering if this is the kind of change we can make during the 4.0
and 4.1 series?  It would be good to be able to rely on SMB signing
against AD DC servers, but unless we apply this patch Samba 4.0 and 4.1
will be exceptions to that unless SMB2 is used. 

But on the flip side, it changes default values during a release train,
and I know that is something we generally don't do.

I would appreciate your thoughts,

Andrew Bartlett

Andrew Bartlett
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT          http://catalyst.net.nz/services/samba

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-lib-param-Consolidate-code-to-enable-smb-signing-on-.patch
Type: text/x-patch
Size: 6787 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20140407/a16b8c13/attachment.bin>

More information about the samba-technical mailing list