rpcrt4: Fixing the using of the auth_len values the wrong way round -…

rpcrt4: Fixing the using of the auth_len values the wrong way round - PKT_PRIVACY implies the packet will be encrypted, not just signed.

rpcrt4: Fixing the using of the auth_len values the wrong way round -…
173590a6 · Rob Shearman · Alexandre Julliard · f8789122 · 173590a6
Commit 173590a6 authored Mar 28, 2007 by Rob Shearman Committed by Alexandre Julliard Mar 28, 2007
Hide whitespace changes
Inline Side-by-side

Showing with 2 additions and 2 deletions

rpc_message.c dlls/rpcrt4/rpc_message.c +2 -2

No files found.
--- a/dlls/rpcrt4/rpc_message.c
+++ b/dlls/rpcrt4/rpc_message.c
@@ -381,9 +381,9 @@ static RPC_STATUS RPCRT4_SendAuth(RpcConnection *Connection, RpcPktHdr *Header,
  else if (Connection->AuthInfo && packet_has_auth_verifier(Header))
  {
    if ((Connection->AuthInfo->AuthnLevel == RPC_C_AUTHN_LEVEL_PKT_PRIVACY) && packet_has_body(Header))
-      Header->common.auth_len = Connection->signature_auth_len;
-    else
      Header->common.auth_len = Connection->encryption_auth_len;
+    else
+      Header->common.auth_len = Connection->signature_auth_len;
  }
  else
    Header->common.auth_len = 0;