r2029: changed our client side dcerpc padding to match what w2k3 does - a 16

byte padding of the payload portion of the packet.
(This used to be commit 271831f97f3952838557bf5034c1e435b33cb14a)

diff --git a/source4/librpc/rpc/dcerpc.c b/source4/librpc/rpc/dcerpc.c
index 0e8828acbdaac532f4ef750ea5e29c9e43b39f9f..31db6df73829ae40a58132466d035e854ec07cf4 100644 (file)
--- a/source4/librpc/rpc/dcerpc.c
+++ b/source4/librpc/rpc/dcerpc.c
@@ -245,8 +245,10 @@ static NTSTATUS dcerpc_push_request_sign(struct dcerpc_pipe *p,
                return status;
        }
 
-       /* pad to 8 byte multiple */
-       p->security_state.auth_info->auth_pad_length = NDR_ALIGN(ndr, 8);
+       /* pad to 16 byte multiple in the payload portion of the
+          packet. This matches what w2k3 does */
+       p->security_state.auth_info->auth_pad_length = 
+               (16 - (pkt->u.request.stub_and_verifier.length & 15)) & 15;
        ndr_push_zero(ndr, p->security_state.auth_info->auth_pad_length);
 
        /* sign or seal the packet */