Nick Gasson wrote in <[email protected]>: |On 11/27/20 05:59 AM, Steffen Nurpmeso wrote: |> Nick Gasson wrote in |> <[email protected]>: |>|Hi, |>| |>|I often need to go through a SOCKS proxy to access certain sites. The |>|diff below adds SOCKS5 support to ftp(1) for HTTP transfers, similar to |>|curl(1). Enabled when http_proxy is set to a socks5:// URL. |>| |>|Also fixes two existing memory leaks: proxyurl (set to NULL on line 646 |>|before freeing) and sslpath (never freed). |>| |>|Tested with ssh -D and a few other SOCKS5 proxies. Also verified the |>|existing HTTP proxy feature still works with squid(8). |> |> By the way, the $SOCKS5_PROXY environment variable becomes used |> for automatic selection of SOCKS5. (Some things on FreeBSD, |> lynx(1), and, hm, the MUA i maintain, s-nail; maybe more.) |> | |(Sorry for the late reply.)
For me - no problem. | |Yes I see FreeBSD fetch added SOCKS5_PROXY recently. I've updated the |diff below to support that too. Anyone interested? Fine. That looks good to me as socks code in general, i do not use named constants because RFC 1928 CONNECT request is the reference, and all SOCKS code is in one function. I also output the errors as strings, for the codes you have to read RFC 1928 yourself, which is pain :) Btw. i see lots of problems with SOCKS5 proxy support of ssh on Linux, i proxy also firefox and we go over wireless on a bad link, and due to the massive parallelization this reaches a hundred concurrent sockets very fast when browsing German/Austrian/English newspapers .. and when ssh gets stuck then we hang 'till the muxer dies. Happens almost every day. 100 should not hit any Linux limit here. But that has nothing to do with OpenBSD and fetch. And you. A nice weekend and Ciao from Germany, --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
