<?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>ill communications &#187; SSH</title>
	<atom:link href="http://illcommunications.com/tag/ssh/feed/" rel="self" type="application/rss+xml" />
	<link>http://illcommunications.com</link>
	<description></description>
	<lastBuildDate>Wed, 08 Sep 2010 04:12:12 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How to enable SSH on a Cisco Router or Switch</title>
		<link>http://illcommunications.com/how-to-enable-ssh-on-a-cisco-router-or-switch/</link>
		<comments>http://illcommunications.com/how-to-enable-ssh-on-a-cisco-router-or-switch/#comments</comments>
		<pubDate>Sat, 25 Apr 2009 01:20:34 +0000</pubDate>
		<dc:creator>Jeff Dimond</dc:creator>
				<category><![CDATA[cisco]]></category>
		<category><![CDATA[how to]]></category>
		<category><![CDATA[Router]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[SSH]]></category>
		<category><![CDATA[Switch]]></category>
		<category><![CDATA[telnet]]></category>

		<guid isPermaLink="false">http://illcommunications.com/?p=118</guid>
		<description><![CDATA[I know a lot of network administrators have long used telnet to remotely manage Cisco routers. My preferred method of accessing these routers remotely is SSH. It is secure and encrypted verses telnet, where all data will be transferred in clear text making it easy for &#8217;sniffers&#8217; to reveal important information that can be used [...]]]></description>
			<content:encoded><![CDATA[<p>I know a lot of network administrators have long used telnet to remotely manage Cisco routers. My preferred method of accessing these routers remotely is SSH. It is secure and encrypted verses telnet, where all data will be transferred in clear text making it easy for &#8217;sniffers&#8217; to reveal important information that can be used in an attack.</p>
<p>Any how let&#8217;s get started.</p>
<p>This assumes you have already logged in to your Cisco router and are in enable mode.</p>
<p>First, you want to check whether SSH has already been enabled.</p>
<pre><code>Router# show ip ssh
%SSH has not been enabled</code></pre>
<p>If you see the result above it obviously means that SSH has not already been enabled on this device.</p>
<p>On with the configuration:</p>
<p>You will want to configure a hostname on your router. This will be performed in configuration mode. (note the prompt)</p>
<pre><code>Router(config)# hostname Router1</code></pre>
<p>The hostname has been set. Now we will configure a domain name for the device.</p>
<pre><code>Router1(config)# ip domain-name Domain1</code></pre>
<p>The domain name has been set. Now we want to generate a RSA key pair.</p>
<pre><code>Router1(config)# crypto key generate rsa modulus 1024</code></pre>
<p>Next we will set a timeout interval.</p>
<pre><code>Router1(config)# ip ssh time-out 120</code></pre>
<p>This will set a time limit of 120 seconds for the SSH session to negotiate.<br />
 You can also set a maximum number of retry attempts incase of a failed negotiation.</p>
<pre><code>Router1(config)# ip ssh authentication-retries 3</code></pre>
<p>This will set the maximum amount of retries to 3.<br />
 The next thing we will do is change the default port for SSH from 22 to 8855. This is not necessary, however I do recommend it for an added level of security.</p>
<pre><code>Router1(config)# ip ssh port 8855</code></pre>
<p>At this time you can log off of the Cisco device and test the connection with a terminal client. In Windows I like to use <a href="http://www.putty.org/">PuTTY</a> and in Linux or OSX I use the ssh command in the terminal.</p>
<p>Once you&#8217;ve logged in and verified the connection is good you can disable telnet access.</p>
<pre><code>Router1(config)# line vty 0 4
Router1(config)# transport input ssh</code></pre>
<p>Now the only way you will be able to remotely access your Cisco device is via SSH on the port you specified earlier, if you opted to change the default port.</p>
<p>Now to save your configuration changes to the Cisco device, you want to save the running-config to the startup config. There are 2 ways of performing this. I will show you both ways, but you should already know this by now.</p>
<p>Option 1</p>
<pre><code>Router1# wr mem</code></pre>
<p>Option 2</p>
<pre><code>Router1# copy running-config startup-config</code></pre>
<p>Now your new configuration should be saved. One last thing we can do to verify SSH configuration is repeat the first command in this tutorial.</p>
<pre><code>Router1# show ip ssh
SSH Enabled - version x.x
Authentication timeout: 120 secs; Authentication retries; 3</code></pre>
<p>We should see the above result with the configuration that we performed.</p>
<p>That concludes setting up SSH access on your Cisco router or switch. I highly recommend using SSH over telnet especially if you will be managing your device remotely. Telnet will give you absolutely no protection from sniffing.</p>
]]></content:encoded>
			<wfw:commentRss>http://illcommunications.com/how-to-enable-ssh-on-a-cisco-router-or-switch/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
