<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Bashton Blog &#187; Tips</title>
	<atom:link href="http://blog.bashton.com/tag/tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.bashton.com</link>
	<description>Bashton Ltd</description>
	<lastBuildDate>Tue, 13 Apr 2010 05:30:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>SSH via another host</title>
		<link>http://blog.bashton.com/2009/ssh-via-another-host/</link>
		<comments>http://blog.bashton.com/2009/ssh-via-another-host/#comments</comments>
		<pubDate>Tue, 04 Aug 2009 08:07:34 +0000</pubDate>
		<dc:creator>sam</dc:creator>
				<category><![CDATA[Tips]]></category>
		<category><![CDATA[netcat]]></category>
		<category><![CDATA[ssh]]></category>

		<guid isPermaLink="false">http://blog.bashton.com/2009/ssh-via-another-host/</guid>
		<description><![CDATA[Many networks have hosts which aren&#8217;t directly accessible via SSH, but have to be connected to via another host.  This can be a pain, especially when one wishes to use scp or sftp.
For a while now I&#8217;ve been using the following in my SSH .config file to allow me to SSH &#8216;directly&#8217; to such hosts:

Host [...]]]></description>
			<content:encoded><![CDATA[<p>Many networks have hosts which aren&#8217;t directly accessible via SSH, but have to be connected to via another host.  This can be a pain, especially when one wishes to use scp or sftp.</p>
<p>For a while now I&#8217;ve been using the following in my SSH .config file to allow me to SSH &#8216;directly&#8217; to such hosts:</p>
<pre>
Host ultimate-destination-name
  ProxyCommand ssh -q intermediary-host nc %h %p $*
  HostName ultimate-destination-host</pre>
<p>Where &#8216;ultimate-destination-name&#8217; is the friendly name for the remote host &#8211; this probably shouldn&#8217;t be a hostname to avoid confusion, &#8216;intermediary-host&#8217; is the Internet-accessible host to connect via, and &#8216;ultimate-destination-host&#8217; is the local hostname/IP for the destination machine, ie what you&#8217;d type after ssh once logged into the intermediary host.<br />
You&#8217;ll need netcat installed on the intermediary host for this to work.</p>
<p>Apart from the obvious advantage of being able to just type &#8217;ssh foo&#8217; to get straight to host foo, this method also allows you to use your local ssh keys without any sort of trust arrangement.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.bashton.com/2009/ssh-via-another-host/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
