<?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>Computer Support &#187; OpenSSH</title>
	<atom:link href="http://www.xiitec.com/blog/tag/openssh/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.xiitec.com/blog</link>
	<description></description>
	<lastBuildDate>Wed, 30 Dec 2009 08:40:28 +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>Setting Up OpenSSH the First Time</title>
		<link>http://www.xiitec.com/blog/2008/02/04/setting-up-openssh-the-first-time/</link>
		<comments>http://www.xiitec.com/blog/2008/02/04/setting-up-openssh-the-first-time/#comments</comments>
		<pubDate>Mon, 04 Feb 2008 21:53:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Remote access]]></category>
		<category><![CDATA[OpenSSH]]></category>

		<guid isPermaLink="false">http://www.xiitec.com/blog/?p=97</guid>
		<description><![CDATA[Install OpenSSH on both machines. sshd, the ssh daemon, must be running on the remote host, so that it can receive connections. Copy the remote host&#8217;s public key to the local machine&#8217;s ~/.ssh/known_hosts file, and you&#8217;re in business.

Starting and stopping sshd on most rpm-based systems is done like this:
# /etc/init.d/sshd start
# /etc/init.d/sshd stop
On Debian, it&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p>Install OpenSSH on both machines. <code>sshd</code>, the ssh daemon, must be running on the remote host, so that it can receive connections. Copy the remote host&#8217;s public key to the local machine&#8217;s <code>~/.ssh/known_hosts </code>file, and you&#8217;re in business.</p>
<p><span id="more-97"></span></p>
<p>Starting and stopping sshd on most rpm-based systems is done like this:</p>
<blockquote><p># /etc/init.d/sshd start<br />
# /etc/init.d/sshd stop</p></blockquote>
<p>On Debian, it&#8217;s slightly different:</p>
<blockquote><p># /etc/init.d/ssh start<br />
# /etc/init.d/ssh stop</p></blockquote>
<p>Always check your init filenames, as they vary on different distributions.</p>
<p>Copying the remote host&#8217;s public key to your local <code>~/.ssh/known_hosts</code> file is as simple as connecting to the remote host:</p>
<blockquote><p>carla@windbag carla$ ssh stinkpad<br />
The authenticity of host &#8217;stinkpad (192.168.1.100)&#8217; can&#8217;t be established.<br />
RSA key fingerprint is a2:c6:70:3e:73:00:b3:ed:90:b1:9a:bc:e7:d5:32:ba.<br />
Are you sure you want to continue connecting (yes/no)?</p></blockquote>
<p>Type yes, and it will respond:</p>
<blockquote><p>Warning: Permanently added &#8217;stinkpad,192.168.1.100&#8242; (RSA) to the list of known hosts.<br />
carla@stinkpad&#8217;s password:<br />
Linux stinkpad 2.4.21 #1 Sun Aug 3 20:15:59 PDT 2003 i686 GNU/Linux<br />
Libranet GNU/Linux<br />
Last login: Sat June  3 22:16:24 2004 from :0.0<br />
carla@stinkpad:~$</p></blockquote>
<p>Using the simple <code>ssh <hostname></hostname></code> login connects you to another host on your LAN, using the same login. You can connect as a different user with the <code>-l</code> flag:</p>
<blockquote><p>carla@windbag ~$ ssh -l wilmaf stinkpad</p></blockquote>
<p>To make an SSH connection over the Internet, you must use the full domain name:</p>
<blockquote><p>carla@windbag ~$ ssh stinkpad.test.net</p></blockquote>
<p>Making that initial connection, and copying the host&#8217;s RSA key, is the riskiest part of setting up SSH. If an intruder managed to compromise your nameserver, she could possibly hijack your SSH session and capture your login. It&#8217;s a pretty small risk, though, and you can verify the IP address before logging in the first time. To close off this hole, you can manually copy the host&#8217;s public key to your local <code>~/.ssh/known_hosts</code> file first. You must edit it slightly; see the examples below.</p>
<p>Host keys are stored in <code>/etc/ssh</code>. These are used to validate the identity of the remote host. This is all you need to allow users to access this machine. All they need is a copy of the public host key in their <code>~/.ssh/known_hosts</code> files and an account to log into. Some Linux distributions create two key pairs when you install OpenSSH—one RSA key pair and one DSA key pair:</p>
<blockquote><p>$ ls /etc/ssh<br />
ssh_host_dsa_key<br />
ssh_host_dsa_key.pub<br />
ssh_host_rsa_key<br />
ssh_host_rsa_key.pub</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.xiitec.com/blog/2008/02/04/setting-up-openssh-the-first-time/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

