Can I somehow do an impromptu VPN with reverse SSH?
@matrix there are at least two ways to do something like that. if you don't want to change the configuration of your computer you can pass a flag to ssh client to create a SOCKS5 proxy. Then configure your browser to use it. I am not sure if it tunnels the DNS but it will tunnel the TCP.
@matrix juhst read a couple guides on it, it used to have to have a browser pref changed in FF to pass the DNS through the tunnel but I think Chrome always does it.
@Moon @matrix I use the dynamic forwarding through SOCKS5 with ssh all the time at work, works great (including DNS). The biggest issue with modern browsers is that they all now by default prevent from connecting to a proxy on localhost because as malware/adware mitigation. In Firefox there's a checkbox in the proxy settings dialog to turn that off, chromium/chrome needs to be launched with a commandline option to turn it off
@Moon @matrix And the chrome/chromium command-line switches would be for example
--proxy-server=socks5://localhost:1080 --proxy-bypass-list='<-loopback>'
The second option takes care of disabling that anti-hijacking thing (what it actually does is /remove/ the loopback interface from the default bypass list)
--proxy-server=socks5://localhost:1080 --proxy-bypass-list='<-loopback>'
The second option takes care of disabling that anti-hijacking thing (what it actually does is /remove/ the loopback interface from the default bypass list)
@pingviini @matrix t4hanks for this info, my version of it was not up to date
@Moon @matrix Funny coincidence, I ran into this at work again today and learned something new:
Chrome on Windows uses Windows' own proxy client stuff, and the bypass list given in that option is in fact fed to the windows proxy client settings. So it only applies on Windows. Also, it's not for allowing to connect to a proxy running on localhost, it's for allowing to access "localhost" (or 127.0.0.1, etc) THROUGH the proxy.
I learned all of this because apparently in certain releases of Windows 10, this is broken :(
Chrome on Windows uses Windows' own proxy client stuff, and the bypass list given in that option is in fact fed to the windows proxy client settings. So it only applies on Windows. Also, it's not for allowing to connect to a proxy running on localhost, it's for allowing to access "localhost" (or 127.0.0.1, etc) THROUGH the proxy.
I learned all of this because apparently in certain releases of Windows 10, this is broken :(
