From: alan (alan@clueserver.org)
Date: Tue Jun 13 2006 - 15:42:48 EDT
On Tue, 13 Jun 2006, Hubert Seiwert wrote:
> When using SSH through the local proxy, it might be an idea to run the
> outside sshd on
> port 443, so it's harder to distinguish from an https server.
Or port 53. That is almost never blocked.
> Also, in case you're not aware, a proxy server on the other side
> (Privoxy in your example)
> is not really necessary - You can use the ssh -D option (or 'Dynamic' in
> the PuTTY port
> forwarding options) to get a SOCKS server on localhost which makes
> outside connections
> through the remote sshd.
If you are running X, you can start up the web app on the other side and
forward the X connection back through the ssh tunnel. Slow, but helpful
when you have to get something done *now* that the censorware is
filtering. (Like renewing your domain registration that expired
yesterday.)
-- "Waiter! This lambchop tastes like an old sock!" - Sheri Lewis ------------------------------------------------------------------------------ This List Sponsored by: Cenzic Concerned about Web Application Security? Why not go with the #1 solution - Cenzic, the only one to win the Analyst's Choice Award from eWeek. As attacks through web applications continue to rise, you need to proactively protect your applications from hackers. Cenzic has the most comprehensive solutions to meet your application security penetration testing and vulnerability management needs. You have an option to go with a managed service (Cenzic ClickToSecure) or an enterprise software (Cenzic Hailstorm). Download FREE whitepaper on how a managed service can help you: http://www.cenzic.com/news_events/wpappsec.php And, now for a limited time we can do a FREE audit for you to confirm your results from other product. Contact us at request@cenzic.com for details. ------------------------------------------------------------------------------
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:56:05 EDT