s4:RPC server - always set the response pad data in base of the request one

Otherwise it could remain uninitialised - should fix bug #7769.

diff --git a/source4/rpc_server/common/reply.c b/source4/rpc_server/common/reply.c
index e5d97d17d15ac524157664311d2a143c8a4d165e..83660c209ba875c5034bfc3ba48ec87f9caab911 100644 (file)
--- a/source4/rpc_server/common/reply.c
+++ b/source4/rpc_server/common/reply.c
@@ -221,6 +221,8 @@ _PUBLIC_ NTSTATUS dcesrv_reply(struct dcesrv_call_state *call)
                pkt.u.response.alloc_hint = stub.length;
                pkt.u.response.context_id = call->pkt.u.request.context_id;
                pkt.u.response.cancel_count = 0;
+               pkt.u.response._pad.data = call->pkt.u.request._pad.data;
+               pkt.u.response._pad.length = call->pkt.u.request._pad.length;
                pkt.u.response.stub_and_verifier.data = stub.data;
                pkt.u.response.stub_and_verifier.length = length;