Blame SOURCES/0014-curl-7.29.0-8ae35102.patch

86693f
From 8683703ef3978983e61329801aecc554aec06055 Mon Sep 17 00:00:00 2001
86693f
From: Daniel Stenberg <daniel@haxx.se>
86693f
Date: Tue, 7 Jan 2014 09:33:54 +0100
86693f
Subject: [PATCH] ConnectionExists: fix NTLM check for new connection
86693f
86693f
When the requested authentication bitmask includes NTLM, we cannot
86693f
re-use a connection for another username/password as we then risk
86693f
re-using NTLM (connection-based auth).
86693f
86693f
This has the unfortunate downside that if you include NTLM as a possible
86693f
auth, you cannot re-use connections for other usernames/passwords even
86693f
if NTLM doesn't end up the auth type used.
86693f
86693f
Reported-by: Paras S
86693f
Patched-by: Paras S
86693f
Bug: http://curl.haxx.se/mail/lib-2014-01/0046.html
86693f
86693f
[upstream commit 8ae35102c43d8d06572c3a1292eb6e27e663c78d]
86693f
86693f
Signed-off-by: Kamil Dudka <kdudka@redhat.com>
86693f
---
86693f
 lib/url.c |    4 ++--
86693f
 1 files changed, 2 insertions(+), 2 deletions(-)
86693f
86693f
diff --git a/lib/url.c b/lib/url.c
86693f
index bddbd91..313ec3e 100644
86693f
--- a/lib/url.c
86693f
+++ b/lib/url.c
86693f
@@ -2782,8 +2782,8 @@ ConnectionExists(struct SessionHandle *data,
86693f
   struct connectdata *check;
86693f
   struct connectdata *chosen = 0;
86693f
   bool canPipeline = IsPipeliningPossible(data, needle);
86693f
-  bool wantNTLM = (data->state.authhost.want==CURLAUTH_NTLM) ||
86693f
-                  (data->state.authhost.want==CURLAUTH_NTLM_WB) ? TRUE : FALSE;
86693f
+  bool wantNTLM = (data->state.authhost.want & CURLAUTH_NTLM) ||
86693f
+    (data->state.authhost.want & CURLAUTH_NTLM_WB) ? TRUE : FALSE;
86693f
   struct connectbundle *bundle;
86693f
 
86693f
   /* Look up the bundle with all the connections to this
86693f
-- 
86693f
1.7.1
86693f