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
imo there should be 2x client side config options.
wget as it is currently setup
ssh -R port is used to create dynamic socks proxy on host and reverse forwarded to server and server uses .js functionality to reproduce wget through the socks proxy
as a work around I have done the following:
Desktop ~/.ssh/config
...
Host *
RemoteForward 54321
...
Remote: ~/bin/wget in which ~/bin is added to PATH via .bashrc
server = 127.0.0.1
server_port = 54321
server_type = 5
note tsocks binary has been scp-ed to ~/bin/tsocks and ~/opt/tsocks/ has been created with libtsocks.so which is normally stored in /usr/lib64/libtsocks.so
This is a work around that allows me to have wget functionality with out messing with anything outside my profile to get it to work (eg: no root required ... even though I have it).
For server hosts in a restricted network it would be nice to be able to
ssh -R port
but wget does not seem to support socks.I tried to put somewhere in my path a shell script named wget - socksifying the original wget but it doesn't seem to get picked up
A preference to use curl or to specify the path to wget would be great
The text was updated successfully, but these errors were encountered: