Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #625676 +++
Description of problem:
I'm unable to use curl with all https:// URLs when my proxy uses kerberos authentization:
curl --proxy http://myproxy:3128 --proxy-negotiate --proxy-user : https://email.seznam.cz
407 Proxy Auth required
when
curl --proxy http://myproxy:3128 --proxy-negotiate --proxy-user : http://email.seznam.cz
works ok.
This bug was already fixed by curl developer(s) in git. Let's see:
https://sourceforge.net/tracker/?func=detail&aid=3046066&group_id=976&atid=100976
I need fix for all supported Fedora and RHEL distributions as soon as possible.
May I add same bug report for RHEL or is this bug report enough for it?
Version-Release number of selected component (if applicable):
$ curl -V
curl 7.19.7 (i386-redhat-linux-gnu) libcurl/7.19.6 NSS/3.12.6.2 zlib/1.2.3 libidn/1.9 libssh2/1.2.4
Protocols: tftp ftp telnet dict ldap ldaps http file https ftps scp sftp
Features: GSS-Negotiate IDN IPv6 Largefile SSL libz
How reproducible:
We have a squid with kerberos authentization.
curl --proxy http://myproxy:3128 --proxy-negotiate --proxy-user : https://email.seznam.cz
407 Proxy Auth required
when
curl --proxy http://myproxy:3128 --proxy-negotiate --proxy-user : http://email.seznam.cz
works ok.
Steps to Reproduce:
1. Install and setup squid with kerberos negotiation auth.
2. curl --proxy http://myproxy:3128 --proxy-negotiate --proxy-user : https://email.seznam.cz
Actual results:
407 Proxy Auth required
Expected results:
Requested page.
Additional info:
This bug was already fixed by curl developer(s) in git. Let's see:
https://sourceforge.net/tracker/?func=detail&aid=3046066&group_id=976&atid=100976
There is official patch in the tracker. I attach the official patch here too.
--- Additional comment from kdudka on 2010-08-20 08:53:08 CEST ---
(In reply to comment #0)
> Created attachment 439865[details]
> patch for the problem created by curl developer
Thanks for filing the bug. Upstream commit:
http://github.com/bagder/curl/commit/13b8fc4> I need fix for all supported Fedora and RHEL distributions as soon as possible.
> May I add same bug report for RHEL or is this bug report enough for it?
I'll clone the bug for RHEL-6. RHEL-5 does not suffer from the flaw as there is no proxy support in http_negotiate at all.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
libcurl was unable to authenticate Kerberos proxies. This is now fixed and libcurl can successfully authenticate Kerberos proxies.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-libcurl was unable to authenticate Kerberos proxies. This is now fixed and libcurl can successfully authenticate Kerberos proxies.+libcurl was unable to authenticate http proxies via Kerberos. This is now fixed and libcurl can successfully authenticate http proxies via Kerberos.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0573.html