<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Securing your SSH access</title>
	<atom:link href="http://switch.richard5.net/2006/09/24/securing-your-ssh-access/feed/" rel="self" type="application/rss+xml" />
	<link>http://switch.richard5.net/2006/09/24/securing-your-ssh-access/</link>
	<description>How to build your Mac into a internet server using open source software</description>
	<lastBuildDate>Tue, 17 Jun 2008 18:25:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Nate Carroll</title>
		<link>http://switch.richard5.net/2006/09/24/securing-your-ssh-access/comment-page-1/#comment-5431</link>
		<dc:creator>Nate Carroll</dc:creator>
		<pubDate>Sat, 04 Nov 2006 19:34:16 +0000</pubDate>
		<guid isPermaLink="false">http://switch.richard5.net/2006/09/24/securing-your-ssh-access/#comment-5431</guid>
		<description>Hi Richard,

I used some software called &quot;Secure Shell Helper&quot; (http://www.gideonsoftworks.com/sshhelper.html) to help secure my Mac mini.  You can turn off password-based SSH logins entirely and generate the required public and private key files for installation on your server and any client computers you&#039;d like to connect from.  And the keys can be encrypted so that they require a separate pass-phrase to be used before a successful connection can be made.  Using key files instead of the normal passwords should potentially protect you more from brute-force dictionary login attacks.

This setup would mean that you can&#039;t connect to your server from just any computer (unless you carry and install the right key file from a flash drive), but if you do most of your administration from one or two laptops, I think it&#039;s a good solution.

-Nate</description>
		<content:encoded><![CDATA[<p>Hi Richard,</p>
<p>I used some software called &#8220;Secure Shell Helper&#8221; (<a href="http://www.gideonsoftworks.com/sshhelper.html" rel="nofollow">http://www.gideonsoftworks.com/sshhelper.html</a>) to help secure my Mac mini.  You can turn off password-based SSH logins entirely and generate the required public and private key files for installation on your server and any client computers you&#8217;d like to connect from.  And the keys can be encrypted so that they require a separate pass-phrase to be used before a successful connection can be made.  Using key files instead of the normal passwords should potentially protect you more from brute-force dictionary login attacks.</p>
<p>This setup would mean that you can&#8217;t connect to your server from just any computer (unless you carry and install the right key file from a flash drive), but if you do most of your administration from one or two laptops, I think it&#8217;s a good solution.</p>
<p>-Nate</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dani</title>
		<link>http://switch.richard5.net/2006/09/24/securing-your-ssh-access/comment-page-1/#comment-3555</link>
		<dc:creator>dani</dc:creator>
		<pubDate>Tue, 26 Sep 2006 16:45:59 +0000</pubDate>
		<guid isPermaLink="false">http://switch.richard5.net/2006/09/24/securing-your-ssh-access/#comment-3555</guid>
		<description>Hi Richard,

I think SSH considers first the config file /etc/sshd_config before it reads the /etc/ssh_config file. It does not overwrite the values already set in /etc/sshd_config with the values you set in /etc/ssh_config. Or I am wrong?

Cheers

Dani</description>
		<content:encoded><![CDATA[<p>Hi Richard,</p>
<p>I think SSH considers first the config file /etc/sshd_config before it reads the /etc/ssh_config file. It does not overwrite the values already set in /etc/sshd_config with the values you set in /etc/ssh_config. Or I am wrong?</p>
<p>Cheers</p>
<p>Dani</p>
]]></content:encoded>
	</item>
</channel>
</rss>

