<?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: Long Term Impact of Youthful Decisions</title>
	<atom:link href="http://emergentchaos.com/archives/2006/10/long-term-impact-of-youthful-decisions.html/feed" rel="self" type="application/rss+xml" />
	<link>http://emergentchaos.com/archives/2006/10/long-term-impact-of-youthful-decisions.html</link>
	<description>The Emergent Chaos Jazz Combo</description>
	<lastBuildDate>Wed, 01 Feb 2012 19:20:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Iang (GP)</title>
		<link>http://emergentchaos.com/archives/2006/10/long-term-impact-of-youthful-decisions.html/comment-page-1#comment-2780</link>
		<dc:creator>Iang (GP)</dc:creator>
		<pubDate>Wed, 25 Oct 2006 06:32:31 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2028#comment-2780</guid>
		<description>I make a similar point in the GP story.  I go a bit further and incorporate the likelihood that the security model first suggested is plain wrong, and also that any costs incurred by security feed materially into reducing the chances of survival of the company.  In fact, employing security in the early days could be the reason that most security-oriented companies fail, which was the observation that got me thinking about it.
The simple hand drawn graphic in &lt;a href=&quot;https://www.financialcryptography.com/mt/archives/000604.html&quot; rel=&quot;nofollow&quot;&gt;GP4.1 Mutual Funds&lt;/a&gt; bears a resemblance to the one above, but is only related, not equivalent.
</description>
		<content:encoded><![CDATA[<p>I make a similar point in the GP story.  I go a bit further and incorporate the likelihood that the security model first suggested is plain wrong, and also that any costs incurred by security feed materially into reducing the chances of survival of the company.  In fact, employing security in the early days could be the reason that most security-oriented companies fail, which was the observation that got me thinking about it.<br />
The simple hand drawn graphic in <a href="https://www.financialcryptography.com/mt/archives/000604.html" rel="nofollow">GP4.1 Mutual Funds</a> bears a resemblance to the one above, but is only related, not equivalent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Molnar</title>
		<link>http://emergentchaos.com/archives/2006/10/long-term-impact-of-youthful-decisions.html/comment-page-1#comment-2779</link>
		<dc:creator>David Molnar</dc:creator>
		<pubDate>Tue, 24 Oct 2006 21:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2028#comment-2779</guid>
		<description>This reminds me of the Gartner analyst&#039;s quote in the NY Times article on contactless credit cards. It sure looks like the card issuers sacrificed encryption of data in favor of time-to-market and hoped no one would notice. One of the differences between credit cards and software, however, is that credit cards stay in place for years and typically can&#039;t be patched short of a reissue...
(Another factor in the credit card case, of course, was that the card companies claimed repeatedly that the data would be encrypted. Too bad it didn&#039;t get implemented that way.)
In any case, there&#039;s probably an interesting WEIS paper that could come out of putting together a model for when it makes sense to defer security expenditure and when not. Do you know if it&#039;s already been written?
</description>
		<content:encoded><![CDATA[<p>This reminds me of the Gartner analyst&#8217;s quote in the NY Times article on contactless credit cards. It sure looks like the card issuers sacrificed encryption of data in favor of time-to-market and hoped no one would notice. One of the differences between credit cards and software, however, is that credit cards stay in place for years and typically can&#8217;t be patched short of a reissue&#8230;<br />
(Another factor in the credit card case, of course, was that the card companies claimed repeatedly that the data would be encrypted. Too bad it didn&#8217;t get implemented that way.)<br />
In any case, there&#8217;s probably an interesting WEIS paper that could come out of putting together a model for when it makes sense to defer security expenditure and when not. Do you know if it&#8217;s already been written?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

