<?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: How To Setup Non-Interactive SSH Login</title>
	<atom:link href="http://www.walkernews.net/2008/06/06/how-to-setup-non-interactive-ssh-login/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.walkernews.net/2008/06/06/how-to-setup-non-interactive-ssh-login/</link>
	<description>A capsule of walker's experience in life...</description>
	<lastBuildDate>Mon, 06 Feb 2012 19:09:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Osher</title>
		<link>http://www.walkernews.net/2008/06/06/how-to-setup-non-interactive-ssh-login/#comment-15089</link>
		<dc:creator>Osher</dc:creator>
		<pubDate>Fri, 17 Jun 2011 09:19:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.walkernews.net/?p=742#comment-15089</guid>
		<description>I encountered another issue that is not mentioned in this guide:

Security requirements implementated in OpenSSH will not accept presented public keys if they can be stolen.
Specifically - when the ~/ directory or the ~/.ssh/ directory of the requesting user is not secured - i.e. chmod to 700 or less.

The observed behavior is that the key was not accepted even through everything was in place and all files were accessible (because permissions were even higher then 700...).

Only by digging in verbose node on the server logs we could see a permissions issue warning, which after hardening permissions first on .ssh folder, and then on home - the silent-login finally worked and scripts started to run well.</description>
		<content:encoded><![CDATA[<p>I encountered another issue that is not mentioned in this guide:</p>
<p>Security requirements implementated in OpenSSH will not accept presented public keys if they can be stolen.<br />
Specifically &#8211; when the ~/ directory or the ~/.ssh/ directory of the requesting user is not secured &#8211; i.e. chmod to 700 or less.</p>
<p>The observed behavior is that the key was not accepted even through everything was in place and all files were accessible (because permissions were even higher then 700&#8230;).</p>
<p>Only by digging in verbose node on the server logs we could see a permissions issue warning, which after hardening permissions first on .ssh folder, and then on home &#8211; the silent-login finally worked and scripts started to run well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Configure Secured Private Key For Password-less SSH Login - Walker News</title>
		<link>http://www.walkernews.net/2008/06/06/how-to-setup-non-interactive-ssh-login/#comment-5626</link>
		<dc:creator>Configure Secured Private Key For Password-less SSH Login - Walker News</dc:creator>
		<pubDate>Mon, 09 Jun 2008 15:49:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.walkernews.net/?p=742#comment-5626</guid>
		<description>[...] enable non-interactive SSH login, you could generate a pair of password-less cryptographic keys for the sake of simplicity, i.e. creates a private key that is not secured with a passphrase (by [...]</description>
		<content:encoded><![CDATA[<p>[...] enable non-interactive SSH login, you could generate a pair of password-less cryptographic keys for the sake of simplicity, i.e. creates a private key that is not secured with a passphrase (by [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

