SSH Tunneling + Proxifier

Fedule

First off, I think this is the right board for this, if it's not, sorry, Boards is big... (Incidentally, if a mod here moves a thread, do I at least get a PM saying where it's gone?)

Second, I am new to anything more complicated than Tor, so apologies in advance for asking stupid questions.

OK.

I have myself a server, to which I have previously logged onto using Putty, so I assume I have everything I need. I'm going to go down what I think I have to do to tunnel all my outgoing traffic, with questions as they arise.

0) Putty is configured with the login details for the proxy.

1) In Putty, fill out details as usual (does the port matter here? I see 22 offered by default)

2) Under SSH/Tunneling, choose a source port (does THIS matter?) and Dynamic destination.

3) Start session, log in per usual. Tunnel is now in operation (right?)

4) Point Proxifier to 127.0.0.1, set it going.

5) Launch... well, whatever.


Should this (in theory) work? Thanks.

MunsterCycling

IBTL

College techs will have you hung, drawn and quartered for trying this.

MC

Fedule

OK, we could get into a big discussion about second guessing what college techs will and won't hang, draw and quarter one for, but that's a seperate matter. Incidentally, in my case (and those of others at my college) they've never intervened in anything other than filesharing.

Should what I posted work?

Sherifu

Fedule wrote: »

(Incidentally, if a mod here moves a thread, do I at least get a PM saying where it's gone?)

Not unless the mod is feeling particularly helpful. Sometimes they may post in thread if they move it.(the good ones will anyway ) If you look up the top left there at the breadcrumbs trail you'll be able to see if it's moved anyway.

What you posted looks fine btw.

Fedule

Sherifu wrote: »

What you posted looks fine btw.

Thanks. Does the choice of ports make a huge difference (ie is it worth choosing anything other than 22 and 8080? I've heard chatter about using 443 instead of 8080...)

MunsterCycling

Sherifu wrote: »

What you posted looks fine btw.

Don't see the words Mod of this section after your name so really we shouldn't second guess what decision will be made but going on previous decisions this will run foul of the rules.

MC

Sherifu

MunsterCycling wrote: »

Don't see the words Mod of this section after your name so really we shouldn't second guess what decision will be made but going on previous decisions this will run foul of the rules.

MC

What are you talking about?

I didn't say whether it's allowed or not. I merely stated it should work from a technical point of view. If you have concerns report the post and stop dragging the thread O/T. You should know how this place works by now

Fedule

Oookay, is discussing tunneling not allowed here? OP cleaned up, in any case.

Khannie

MunsterCycling wrote: »

Don't see the words Mod of this section after your name so really we shouldn't second guess what decision will be made but going on previous decisions this will run foul of the rules.

MC

Discussions of tunneling are fine (as are discussions of torrents and any other technology with a legitimate use). Tunneling's a great technology. I use it _every_ day.

OP: Your setup sounds fine. If you're going to proxy web traffic, the SSH server on linux boxes has built in SOCKS proxy support. Consider using compression on the connection if the remote machine is far away.

Kinetic^

Sorry to hijack but got any decent guides to tunnelling?

FruitLover

You've probably seen people discussing ports like 80, 443 (and possibly 8080) because these ports could be less likely to be filtered than e.g. the standard SSH port. This is a setting that would need to be changed on the server though. If you're able to get a connection on port 22, you don't need to worry about that.

Your source port doesn't matter (although some OS won't let a non-admin user open a local port below 1024).

MunsterCycling wrote: »

Don't see the words Mod of this section after your name so really we shouldn't second guess what decision will be made but going on previous decisions this will run foul of the rules

I see you're no stranger to the mod back seat yourself :rolleyes:

MunsterCycling

Go pick some other Fruit as you are barking up the wrong tree :P,
I reported the post early this morning as the OP is asking for this info to breach college policy so as to play games using college equipment, which if it was in a business setting would be a serious disciplinary issue

How is this any different? http://www.boards.ie/vbulletin/showthread.php?t=2055681454

Khannie

MunsterCycling wrote: »

How is this any different? http://www.boards.ie/vbulletin/showthread.php?t=2055681454

This thread asks a general question about tunneling, the other thread explicity asks a question about circumventing a businesses firewall.

It's like threads on torrenting v's threads on getting episodes of lost through torrents. It's a somewhat fine line I grant you but there you have it.

Fedule

Ok, thanks all so far, but I need to double check the Destination field in Putty (Note that I haven't actually tried running this since I won't have access to the machine I want to use for another week). Currently I have it blank with Dynamic checked below this. But everything I've been reading about SSH tunnels (which usually involves specific applications like mail clients) talks about filling that out and choosing Local. I understand Destination refers to another machine+port for the connection to be forwarded to, but I'm connecting to a server I want to use as a proxy. So what, exactly do I do with this field? I'm told so far in this thread that what I've posted will work... but maybe one more reassurance is needed?