<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Automatic proxy configuration and SSH tunneling</title>
	<link>http://www.summersault.com/community/weblog/2005/02/19/automatic-proxy-configuration-and-ssh-tunneling.html</link>
	<description>The weblog for Summersault, LLC, a website development firm in Richmond, Indiana</description>
	<pubDate>Thu, 28 Aug 2008 18:42:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1.3</generator>

	<item>
		<title>by: Mark Stosberg</title>
		<link>http://www.summersault.com/community/weblog/2005/02/19/automatic-proxy-configuration-and-ssh-tunneling.html#comment-2</link>
		<pubDate>Sat, 19 Feb 2005 21:35:16 +0000</pubDate>
		<guid>http://www.summersault.com/community/weblog/2005/02/19/automatic-proxy-configuration-and-ssh-tunneling.html#comment-2</guid>
					<description>Another way to make this even easier is  to add the tunnelling details to .ssh/config, where you can forget about them:

Host shortname shortname.companyname.com
        Hostname shortname.companyname.com
        User myuser
        LocalForward 8000   webproxy:80
</description>
		<content:encoded><![CDATA[	<p>Another way to make this even easier is  to add the tunnelling details to .ssh/config, where you can forget about them:</p>
	<p>Host shortname shortname.companyname.com<br />
        Hostname shortname.companyname.com<br />
        User myuser<br />
        LocalForward 8000   webproxy:80
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
