If the ssh server is already setup on the server side, ie you can log in via ssh, then nothing additional should be needed to use the Socks setup. You don't need that if you're using the ssh server as a Socks proxy. The google search you linked shows mostly setups using Squid which is an actual proxy server and that would require setting up squid on the server side. That's all you should have to do for it to work. I just submitted ticket with my server's support company on that, and they said they could set it up to work (we'll still in the Q&A fase). Would you know if that would be all that needs to be done for it to work? I've been researching the crap out of it, and it looks like the server might also need to be configured for it to work: This sends all your browser traffic to localhost:9999 where ssh is listening and it forwards it on to. Then in your web browser proxy settings you put localhost as the socks host and 9999 as the port. This tells ssh to listen on localhost:9999 for traffic and send anything it gets to. you use the first command to establish the tunnel from port 9999 on localhost to. Ssh -ND 9999 -ND 9999 wouldn't go in either. That all sounds good.but I think that the proxy host should be localhost instead of the actual server you are connecting to such as. I'll play with that when I have some more time tomorrow. It also appears that I can configure the System Prefs/Network to connect all internet connections to go through /9999. Ssh -ND 9999 point the advanced settings in the prefs for Safari to connect via proxy to / port 999, and that should do it. That is the host that the terminal is outputting for you to connect to. Also from that article I think you would actually change the proxy host to localhost. Check your ip address before you enable all that and then after to see if it changed. You were typing ssh -ND 9999 from your Mac to log into your server. Edited Jby mjohns930ĮTA: Ok I think I misunderstood. There won't be anything happening.ĮTA: Ok I think I misunderstood. Your terminal on your Mac will simply give you a prompt and that's it, just like SSHing into your server regularly. Then you go into Firefox and change the proxy settings. Although I would not SSH in as root, that is entirely up to you. That will SSH you into your server as root and set up the proxy on your Mac on port 9999. Ok, you will actually type ssh -ND 9999 from your Mac. It doesn't look like I'm doing anything in Terminal? Ssh -ND 9999 configure my computor's Network Settings to connect via proxy / port 9999.
So from that article, does this sound correct if I SSH into my () server as "root." At the command line I'd enter: You also don't need Putty as OSX has a terminal, so it's a quick command away to do this. And like I said I am confident this can be adapted to an OSX machine.ĮTA: Ok.so I did a quick search and I found this () article which does go into how to do this on a Mac. This (, PDF) probably explains it a little better. All the traffic goes through my Ubuntu Server first and then to my computer I am using. Then change the proxy settings on my browser or IM client or whatever I am using and then it connects over a secure SSH tunnel. I then SSH into the machine with Putty and set Putty up to act as my proxy.
The most important thing you need running on it for this is Open SSH Server. I have a low power Intel Atom based machine running all the time at my apartment with Ubuntu Linux Server on it. Now if you are looking for something along the lines of security and anonymity when say browsing from an open public hotspot this is what I do, granted it's on a Windows machine, but I am confident there is a similar way to do this on a Mac. But if it is a caching proxy you are looking for here () is a pretty helpful article. A locally attached caching proxy is pretty cool.but I would assume (probably incorrectly) that you are looking for something along the lines of security and anonymity on the internet.
0 kommentar(er)
