Bug 953864
Summary: | NTLM broken in Curl 7.19.7-35.el6.x86_64 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Ruben Püttmann <ruben> |
Component: | curl | Assignee: | Kamil Dudka <kdudka> |
Status: | CLOSED DUPLICATE | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-04-20 08:47:31 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ruben Püttmann
2013-04-19 11:10:17 UTC
(In reply to comment #0) > Description of problem: > > with the curl version distributed with 6.4 it is not possible to do an ntlm > authentification. Unlikely. The support for NTLM was introduced in curl-7.19.7-16.el6 (bug #606819) and covered by regression tests. > Upstream is fixed. See also: > > http://stackoverflow.com/questions/4341368/curl-always-returns-401-with-ntlm > http://serverfault.com/questions/408421/ntlm-with-curl-returns-401 Those builds use OpenSSL-powered NTLM authentication whereas we use NSS. > How reproducible: > > > curl https://exchangserver/EWS/Exchange.asmx [^] -w %{http_code} --ntlm -u > username --verbose --show-error > > It will ask you for your password. On centos with curl 7.19.7-35.el6.x86_64 > I got an 401 on my debian box with Please provide a self-contained reproducer. I will send you an E-mail with some additional Informations, including some non public stuff. The Patch from: https://bugzilla.redhat.com/show_bug.cgi?id=799557 fixes teh problem here Thank you for confirming the fix! I am closing this bug as duplicate... *** This bug has been marked as a duplicate of bug 799557 *** |