<?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: Silencing pointless reverse DNS warnings from OpenSSH</title>
	<atom:link href="http://www.pervasivecode.com/blog/2008/05/22/silencing-pointless-reverse-dns-warnings-from-openssh/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pervasivecode.com/blog/2008/05/22/silencing-pointless-reverse-dns-warnings-from-openssh/</link>
	<description>Jamie Flournoy's Software Development Blog</description>
	<lastBuildDate>Mon, 02 Aug 2010 14:57:29 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Steve Laesch</title>
		<link>http://www.pervasivecode.com/blog/2008/05/22/silencing-pointless-reverse-dns-warnings-from-openssh/comment-page-1/#comment-33099</link>
		<dc:creator>Steve Laesch</dc:creator>
		<pubDate>Mon, 02 Aug 2010 14:57:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.pervasivecode.com/blog/2008/05/22/silencing-pointless-reverse-dns-warnings-from-openssh/#comment-33099</guid>
		<description>Thank you thank you thank you thank you thank you.

We routinely ssh to systems hosted by a provider that is notoriously bad about maintaining proper PTR records, so I&#039;m accustomed to seeing the POSSIBLE BREAK-IN ATTEMPT! messages every time I login. There isn&#039;t much point in having the provider fix the way the systems are listed in DNS because we&#039;re the only people that access these systems in this manner. We have scripts that access multiple systems in an automated fashion and provide information. The POSSIBLE BREAK-IN ATTEMPT messages really mess up the way the information is presented. We could use 2&gt; /dev/null, of course, but this (turning off GSSAPIAuthentication) is a better way to do it.</description>
		<content:encoded><![CDATA[<p>Thank you thank you thank you thank you thank you.</p>
<p>We routinely ssh to systems hosted by a provider that is notoriously bad about maintaining proper PTR records, so I&#8217;m accustomed to seeing the POSSIBLE BREAK-IN ATTEMPT! messages every time I login. There isn&#8217;t much point in having the provider fix the way the systems are listed in DNS because we&#8217;re the only people that access these systems in this manner. We have scripts that access multiple systems in an automated fashion and provide information. The POSSIBLE BREAK-IN ATTEMPT messages really mess up the way the information is presented. We could use 2&gt; /dev/null, of course, but this (turning off GSSAPIAuthentication) is a better way to do it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Horton</title>
		<link>http://www.pervasivecode.com/blog/2008/05/22/silencing-pointless-reverse-dns-warnings-from-openssh/comment-page-1/#comment-9022</link>
		<dc:creator>Josh Horton</dc:creator>
		<pubDate>Thu, 03 Jul 2008 06:07:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.pervasivecode.com/blog/2008/05/22/silencing-pointless-reverse-dns-warnings-from-openssh/#comment-9022</guid>
		<description>Thank you for the quick answer to this annoying error msg.</description>
		<content:encoded><![CDATA[<p>Thank you for the quick answer to this annoying error msg.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
