<?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: Xero Security</title>
	<atom:link href="http://blog.xero.com/2008/07/xero-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.xero.com/2008/07/xero-security/</link>
	<description>Xero Accounting Software</description>
	<lastBuildDate>Wed, 08 Feb 2012 18:47:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bwooce</title>
		<link>http://blog.xero.com/2008/07/xero-security/comment-page-1/#comment-188</link>
		<dc:creator>Bwooce</dc:creator>
		<pubDate>Sun, 27 Jul 2008 10:08:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xero.com/?p=311#comment-188</guid>
		<description>Well done on attacking it front on. Security is turning into another hygiene factor for all software, forcing us all (reqs, arch, design, code, test) to be more security aware.

PS. Surely &quot;foolproof&quot; not &quot;full proof&quot;?</description>
		<content:encoded><![CDATA[<p>Well done on attacking it front on. Security is turning into another hygiene factor for all software, forcing us all (reqs, arch, design, code, test) to be more security aware.</p>
<p>PS. Surely &#8220;foolproof&#8221; not &#8220;full proof&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Business Tracking Software</title>
		<link>http://blog.xero.com/2008/07/xero-security/comment-page-1/#comment-183</link>
		<dc:creator>Business Tracking Software</dc:creator>
		<pubDate>Thu, 24 Jul 2008 19:34:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xero.com/?p=311#comment-183</guid>
		<description>Sounds like a good software application. I found the last part of your article helpful as you outline ways for users to help keep the software secure.

This seems like general advice that would be good to apply to any type of secure software or application employees may be working with. Thanks for the good ideas.</description>
		<content:encoded><![CDATA[<p>Sounds like a good software application. I found the last part of your article helpful as you outline ways for users to help keep the software secure.</p>
<p>This seems like general advice that would be good to apply to any type of secure software or application employees may be working with. Thanks for the good ideas.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

