<?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 for Out with the new, in with the old</title>
	<atom:link href="http://www.gryman.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gryman.com</link>
	<description>The views of an American</description>
	<lastBuildDate>Sat, 05 Jun 2010 00:24:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on Website Security Flaw for Craig Hunter by Greg</title>
		<link>http://www.gryman.com/2010/06/website-security-flaw-for-craig-hunter/comment-page-1/#comment-5</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Sat, 05 Jun 2010 00:24:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryman.com/?p=54#comment-5</guid>
		<description>Leaving an editor such as fckeditor open without any protection is a security flaw that could be exploited. Yes, they could put an index file there to keep eyes away from what&#039;s there, but anyone who knows the directory and file structure could still find the files and exploit them. The correct thing to do is to setup some form of password protection keeping the public away from the editor. This really is very basic web knowledge that anyone and everyone should know when it comes to websites, especially high profile sites.

It does appear to be fixed now, which is good, and likely took them a whole two seconds to throw up a .htaccess file limiting access.</description>
		<content:encoded><![CDATA[<p>Leaving an editor such as fckeditor open without any protection is a security flaw that could be exploited. Yes, they could put an index file there to keep eyes away from what&#8217;s there, but anyone who knows the directory and file structure could still find the files and exploit them. The correct thing to do is to setup some form of password protection keeping the public away from the editor. This really is very basic web knowledge that anyone and everyone should know when it comes to websites, especially high profile sites.</p>
<p>It does appear to be fixed now, which is good, and likely took them a whole two seconds to throw up a .htaccess file limiting access.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Website Security Flaw for Craig Hunter by what</title>
		<link>http://www.gryman.com/2010/06/website-security-flaw-for-craig-hunter/comment-page-1/#comment-4</link>
		<dc:creator>what</dc:creator>
		<pubDate>Sat, 05 Jun 2010 00:00:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryman.com/?p=54#comment-4</guid>
		<description>I don&#039;t see this? Looks they already fixed the problem(?), seems they&#039;re pretty on the ball to me.

And from what I know of web design.. this isn&#039;t a security flaw at all. That&#039;s a standard function for the web server, they probably could have thrown an index file in there, but there was nothing particularly deadly by showing a fckeditor directory. Please correct me if I&#039;m wrong?

I&#039;m all for bashing a candidate, but usually I try to make it about something valid, and that they actually did wrong. Just saying my $0.02</description>
		<content:encoded><![CDATA[<p>I don&#8217;t see this? Looks they already fixed the problem(?), seems they&#8217;re pretty on the ball to me.</p>
<p>And from what I know of web design.. this isn&#8217;t a security flaw at all. That&#8217;s a standard function for the web server, they probably could have thrown an index file in there, but there was nothing particularly deadly by showing a fckeditor directory. Please correct me if I&#8217;m wrong?</p>
<p>I&#8217;m all for bashing a candidate, but usually I try to make it about something valid, and that they actually did wrong. Just saying my $0.02</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on If you don&#8217;t like guns&#8230; Don&#8217;t get one! by James Tippins</title>
		<link>http://www.gryman.com/2009/10/if-you-dont-like-guns-dont-get-one/comment-page-1/#comment-2</link>
		<dc:creator>James Tippins</dc:creator>
		<pubDate>Sun, 04 Oct 2009 05:32:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryman.com/?p=36#comment-2</guid>
		<description>I have to say Greg, this is a superb video from many angles, I&#039;m going to snag it and play it for some folks!</description>
		<content:encoded><![CDATA[<p>I have to say Greg, this is a superb video from many angles, I&#8217;m going to snag it and play it for some folks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
