You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Privproxy is one way to do this, but newer versions of tinyproxy also can do this. In PP01, we have used privproxy as documented below.
privproxy allows us to have a socks5 upstream to an http proxy, which is convenient for tools that do not work will with proxychains or have built in support for socks proxies.
Privroxy is packaged, however, it installs as a broken package. It is broken because the daemon is started in the configuration stage of packaging, where it tries to listen on ::1 in addition to localhost. Fixing this in the configuration file allows it to start and an "apt-get -f install" will restore the packaging system to working.
By putting a line like below at the end of the config file, we have an http proxy going to a socks upstream. forward-socks4 / 192.168.2.11:8003 .
The text was updated successfully, but these errors were encountered:
Privproxy is one way to do this, but newer versions of tinyproxy also can do this. In PP01, we have used privproxy as documented below.
privproxy allows us to have a socks5 upstream to an http proxy, which is convenient for tools that do not work will with proxychains or have built in support for socks proxies.
Privroxy is packaged, however, it installs as a broken package. It is broken because the daemon is started in the configuration stage of packaging, where it tries to listen on ::1 in addition to localhost. Fixing this in the configuration file allows it to start and an "apt-get -f install" will restore the packaging system to working.
By putting a line like below at the end of the config file, we have an http proxy going to a socks upstream.
forward-socks4 / 192.168.2.11:8003 .
The text was updated successfully, but these errors were encountered: