Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#65752 - [curl] Can't resolv when a socks proxy is configured

Attached to Project: Arch Linux
Opened by Cedric Bellegarde (gnumdk) - Monday, 09 March 2020, 12:40 GMT
Last edited by Christian Hesse (eworm) - Wednesday, 11 March 2020, 08:31 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
When using a socks proxy, since 7.69, resolver is broken.

Additional info:
* package version(s) 7.69.0-3
* config and/or log files etc.
* link to upstream fix: https://github.com/curl/curl/commit/f0e81605451b363617889820e17a35c262fdee78

Steps to reproduce:

LANG=C curl -vvv linuxfr.org
* Uses proxy env variable all_proxy == 'socks://127.0.0.1:8080/'
* Trying 127.0.0.1:8080...
* SOCKS4 communication to linuxfr.org:80
* SOCKS4 non-blocking resolve of linuxfr.org
* Closing connection 0
curl: (6) Couldn't resolve host name
This task depends upon

Closed by  Christian Hesse (eworm)
Wednesday, 11 March 2020, 08:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  curl-7.69.1-1
Comment by AMM (amish) - Wednesday, 11 March 2020, 03:13 GMT
Socks4 was fixed but not socks5 (exact same bug). Upstream fix https://github.com/curl/curl/commit/4b786abc434d9802229d08d625acbf8cbb9d326f

Upstream issue: https://github.com/curl/curl/issues/5053
Socks5 bug was originally reported and fixed as developers did not know that same bug exists for socks4. And socks4 bug was fixed later.

Loading...