Well you need to tell the person who wrote it... On 1 Jun 2005 15:02:32 -0000, wayne <wayne@xxxxxxxxxxxxx> wrote: > > > > AgentSmith15 wrote: > > I loved this guide, I'm sure you guys will too. > > Also please help support the site by clicking on the ads. > > http://www.buzzsurf.com/surfatwork/ > > I like the presentation (much better then anything I did!), but it looks > like the author has missed out on helping a large percentage of his > audience. I see mention in the change log that he realizes that a tunnel can > be set up through a proxy server, so he removes 'proxies' from the 'when > this won't work' section, but there's no followup to tell people how it's > done! > Most people would be in that situation these days, i think. > > Anyway, here's what you need to add to the instructions there *if* your > corp/school net uses a proxy and blocks all outgoing tcp direct connections. > > First, let me say I don't often use putty. Normally I would use a > ssh/cygwin combination on ms windows. It's possible that putty has the > following stuff in it, but i doubt that. > > The problem would be that as soon as you > ssh -D port <home:443> > you'd find the connection just times out. > Port 443 (and 80, 8080, etc.) are most likely blocked. > > What's needed then is a program to set up that connection for you first. > It can often be done using a CONNECT through the proxy, since they almost > always allow connections to 443. This is why Panix, for example, was always > my top recommendation if you didn't have a home (or a friend's) computer to > use. $100 a year though :-( > They run a sshd on port 443, so proxies will allow you to CONNECT there. > > My searches were done 2 years ago (when the ssh -D option was first > introduced); there may be better options now. > This is what I'm still using though - it works well. > See the list archives for my more detailed descriptions of how to set it > up. > > Go get something like connect.exe from > http://www.taiyo.co.jp/~gotoh/ssh/connect.exe > (and numerous other sites) > and then put something like > Host your.outside.server > ProxyCommand connect.exe -H your.proxy.host:8888 %h %p > in the configuration file for ssh (putty?). > > What happens then is that connect.exe runs to CONNECT thru your proxy to > the external sshd, and waits while ssh (putty) makes it's encrypted tunnel > over that connection. > > The instructions on the site mentioned above are then still the same ... > > ===8>============== noCensorship community =============== > List's webpage: //www.freelists.org/webpage/nocensorship > List's archive: //www.freelists.org/archives/nocensorship > To unsubscribe: nocensorship-request@xxxxxxxxxxxxx with 'unsubscribe' in > the SUBJECT field. > Moderator's email: nocensorship-moderators@xxxxxxxxxxxxx > ===8>============== noCensorship community =============== > > > ===8>============== noCensorship community =============== List's webpage: //www.freelists.org/webpage/nocensorship List's archive: //www.freelists.org/archives/nocensorship To unsubscribe: nocensorship-request@xxxxxxxxxxxxx with 'unsubscribe' in the SUBJECT field. Moderator's email: nocensorship-moderators@xxxxxxxxxxxxx ===8>============== noCensorship community ===============