<?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: Software Liability = Our Worst Nightmare</title>
	<atom:link href="http://spiresecurity.com/?feed=rss2&#038;p=632" rel="self" type="application/rss+xml" />
	<link>http://spiresecurity.com/?p=632</link>
	<description>Risk and Cybersecurity Analysis</description>
	<lastBuildDate>Wed, 21 Aug 2013 23:28:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Stuart Berman</title>
		<link>http://spiresecurity.com/?p=632&#038;cpage=1#comment-888</link>
		<dc:creator>Stuart Berman</dc:creator>
		<pubDate>Wed, 02 Mar 2005 03:50:06 +0000</pubDate>
		<guid isPermaLink="false">http://spiresecurity.com/blog/?p=632#comment-888</guid>
		<description><![CDATA[Whew! Nice to hear such clarity on liability.

I am very skeptical about the ability to clean up the coding since features always trump design in our free market society - for a nice European persective on the &#039;right way&#039; to write code see Clive Robinson&#039;s comment at:
http://www.schneier.com/blog/archives/2005/02/regulation_liab.html#comments
IMHO his advice is DOA (even a fine German company like SAP has some of the craziest spaghetti code imaginable). I say that as someone who has tried to secure common applications only to repeatedly discover that vendors can&#039;t tell you have their applications really function - such as reading a Microsoft paper on what network ports are needed for an application (they specify unneeded ports and forget others that are critical).
The best I can imagine is that we manage the risk and those whose governance (or luck) fail them will go extinct as &#039;better&#039; solutions come along. (Will we see that with Microsoft losing market share to Firefox or Apple?)

]]></description>
		<content:encoded><![CDATA[<p>Whew! Nice to hear such clarity on liability.</p>
<p>I am very skeptical about the ability to clean up the coding since features always trump design in our free market society &#8211; for a nice European persective on the &#8216;right way&#8217; to write code see Clive Robinson&#8217;s comment at:<br />
<a href="http://www.schneier.com/blog/archives/2005/02/regulation_liab.html#comments" rel="nofollow">http://www.schneier.com/blog/archives/2005/02/regulation_liab.html#comments</a><br />
IMHO his advice is DOA (even a fine German company like SAP has some of the craziest spaghetti code imaginable). I say that as someone who has tried to secure common applications only to repeatedly discover that vendors can&#8217;t tell you have their applications really function &#8211; such as reading a Microsoft paper on what network ports are needed for an application (they specify unneeded ports and forget others that are critical).<br />
The best I can imagine is that we manage the risk and those whose governance (or luck) fail them will go extinct as &#8216;better&#8217; solutions come along. (Will we see that with Microsoft losing market share to Firefox or Apple?)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
