Using the option "--proxy-ntlm" leads to the following error: curl: option --proxy-ntlm: the installed libcurl version doesn't support this `equery uses curl` yields: - - ares : Enabled c-ares dns support + + gnutls : Adds support for net-libs/gnutls + + idn : Enable support for Internationalized Domain Names + + ipv6 : Adds support for IP version 6 + + kerberos : Adds kerberos support + + ldap : Adds LDAP support (Lightweight Directory Access Protocol) + + ssl : Adds support for Secure Socket Layer connections - - test : Workaround to pull in packages needed to run with FEATURES=maketest / FEATURES=test Reproducible: Always Steps to Reproduce:
I found the problem. I have both 'gnutls' and 'ssl' enabled as use flags. This causes the '--without-ssl' to be used during configure which prevent '--proxy-ntlm' from working. Removing the gnutls use flag for curl solved the problem. Is this desired/expected behaviour?
dragonheart - can you take this one? Re-assigning wrt Bug 171155
(In reply to comment #1) > I found the problem. I have both 'gnutls' and 'ssl' enabled as use flags. This > causes the '--without-ssl' to be used during configure which prevent > '--proxy-ntlm' from working. Removing the gnutls use flag for curl solved the > problem. > > Is this desired/expected behaviour? > Yes this is the functionally that upstream built. I just tested with the CVS version of curl and gnutls doesn't support proxy ntlm authentication.
confirmed as per URL. FAQ updated in next curl version. It is possible to patch Curl to have a GnuTLS NTLM version as Daniel Bagder mentions so if you're up for a programming challenge feel free to attach a patch to the sf bugtrack pages.
