The socks.c code shows that cURL does not even attempt DNS resolution on
SOCKS4a. Strictly speaking, the SOCKS4a spec expects apps to /attempt/
DNS resolution before contacting the socks server. I won't complain on
this point though because the status quo is favorable to Tor users (as
it
According to the SOCKS4a spec:
https://www.openssh.com/txt/socks4.protocol
https://www.openssh.com/txt/socks4a.protocol
With SOCKS4 cURL *must* do DNS resolution and pass the selected IP to
the SOCKS server. OTOH, SOCKS4a gives cURL the option to resolve. If
cURL fails at DNS resolution,
2 matches
Mail list logo
