From fa24196d0d5c7373317894865b7a88d972762101 Mon Sep 17 00:00:00 2001 From: Stefan Metzmacher Date: Tue, 10 May 2005 11:04:04 +0000 Subject: r6705: let the gensec module decide if messages can be signed and sealed in a different order than a strict request - reply sequence Note: we should also fix the client code... metze (This used to be commit 0a61d1f65150546f7a7582512ca010d156f963bf) --- source4/rpc_server/dcerpc_server.c | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'source4/rpc_server/dcerpc_server.c') diff --git a/source4/rpc_server/dcerpc_server.c b/source4/rpc_server/dcerpc_server.c index cb1cdc9416..12e24859ec 100644 --- a/source4/rpc_server/dcerpc_server.c +++ b/source4/rpc_server/dcerpc_server.c @@ -742,6 +742,10 @@ static NTSTATUS dcesrv_request(struct dcesrv_call_state *call) call->state_flags = call->conn->dce_ctx->state_flags; call->time = timeval_current(); + if (!gensec_have_feature(call->conn->auth_state.gensec_security, GENSEC_FEATURE_ASYNC_REPLIES)) { + call->state_flags &= ~DCESRV_CALL_STATE_FLAG_MAY_ASYNC; + } + context = dcesrv_find_context(call->conn, call->pkt.u.request.context_id); if (context == NULL) { return dcesrv_fault(call, DCERPC_FAULT_UNK_IF); -- cgit