On Tue, 6 Nov 2001, Mansur, Warren wrote: > The http proxy server where I work is absolutely > terrible. Half the time it reports that the page timed out, and most of > the time I have to go to the page twice to get it to load.
Gee... sounds like Microsoft Proxy Server! Or "Internet Security and Acceleration Server" as it is called in its latest incarnation. > So, here's one solution I thought of. Perhaps I could have a my own > proxy server, which when asked for a page, would go over port 22 (the > ssh port) to my home computer. They block 80, but allow 22? That's... interesting. Anyway: If so much as one TCP port is open to the Internet, you basically can do anything you want. All you have to do is run an IP-over-IP tunnel to the outside, and you just punched a hole a mile wide through the firewall. You could also just run an HTTP proxy on port 22 on your system, and avoid the overhead of SSH. Of course, you also avoid the security. And, of course, you could be unimaginative, and use SSH port forwarding to connect your work system to your home system's HTTP proxy. Keep in mind, any or all of these may violate corporate policy. In some places, such things can get you fired. Use caution. -- Ben Scott <[EMAIL PROTECTED]> | The opinions expressed in this message are those of the author and do not | | necessarily represent the views or policy of any other person, entity or | | organization. All information is provided without warranty of any kind. | ***************************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *****************************************************************
