rpcrt4: Fixing the using of the auth_len values the wrong way round
- PKT_PRIVACY implies the packet will be encrypted, not just signed.
Robert Shearman
rob at codeweavers.com
Wed Mar 28 02:57:49 CDT 2007
---
dlls/rpcrt4/rpc_message.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
-------------- next part --------------
diff --git a/dlls/rpcrt4/rpc_message.c b/dlls/rpcrt4/rpc_message.c
index 53d191b..1086602 100644
--- a/dlls/rpcrt4/rpc_message.c
+++ b/dlls/rpcrt4/rpc_message.c
@@ -381,9 +381,9 @@ static RPC_STATUS RPCRT4_SendAuth(RpcCon
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;
More information about the wine-patches
mailing list