Am Sun, 5 Jan 2025 16:55:57 -0800 (PST)
schrieb Chime Hart <ch...@hubert-humphrey.com>:
> Granted that comes from a 2016 story. Lynx cannot connect-and-I am
> not familliar with tor, although I have it installed. Thanks so much
> in advance for any guidance
-socks5_proxy=URL
(Via which) SOCKS5 proxy to connect: any network traffic,
including all DNS resolutions but the one for URL itself, will be
redirected through the SOCKS5 proxy. URL may be given as
“proxy.example.com”, “proxy.example.com:1080”, “192.168.0.1”, or
“192.168.0.1:1080” (and IPv6 notation if so supported). A SOCKS5
proxy may also be specified via the environment variable
SOCKS5_PROXY. This option controls the builtin SOCKS5 support,
which is unrelated to the option -nosocks.
lynx supports using a SOCKS proxy.
The TOR client (not the TOR browser bundle) offers a service
permanently running on localhost TCP port 9050. See /etc/tor/torrc for
configuring the listening addresses and port and also the machines that
are allowed to connect if you want to use the TOR service on another
computer in your network.
The TBB starts another TOR client on 9150 when running, but will stop
when TBB closes.
Here is an example:
lynx
-socks5_proxy="127.0.0.1:9150"
http://2gzyxa5ihm7nsggfxnu52rck2vv4rvmdlkiu3zzui5du4xyclen53wid.onion/index.html
The onion URL you posted is old and not supported anymore.
