<?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: Eric Drexler blogging</title>
	<atom:link href="http://emergentchaos.com/archives/2008/12/eric-drexler-blogging.html/feed" rel="self" type="application/rss+xml" />
	<link>http://emergentchaos.com/archives/2008/12/eric-drexler-blogging.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: nick</title>
		<link>http://emergentchaos.com/archives/2008/12/eric-drexler-blogging.html/comment-page-1#comment-5304</link>
		<dc:creator>nick</dc:creator>
		<pubDate>Tue, 23 Dec 2008 19:30:16 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2973#comment-5304</guid>
		<description>Adam,
The number of people who install s/w on their cell phones and cameras are miniscule, compared to those who install s/w on their PCs.  If/when it ever becomes common practice, and is done in the unprotected Unix/Windows style, we will see viruses galore on cell phones and cameras.
I&#039;m not proposing to eliminate USB keys.  Quite the contrary, I&#039;m proposing to make flash drives secure, something Windows and Unix can&#039;t do.  I&#039;m proposing to eliminate autorun.inf files, boot sectors, and other common executables that can be written to by any other than the authorized distributor of the original code or a very limited set of agents authorized by same, and to run all other executables in extremely restrictive sandboxes.  Nothing complicated or &quot;halting&quot; about this at all.  It just happens to be radically different from how the Unix world and Microsoft currently do business.
</description>
		<content:encoded><![CDATA[<p>Adam,<br />
The number of people who install s/w on their cell phones and cameras are miniscule, compared to those who install s/w on their PCs.  If/when it ever becomes common practice, and is done in the unprotected Unix/Windows style, we will see viruses galore on cell phones and cameras.<br />
I&#8217;m not proposing to eliminate USB keys.  Quite the contrary, I&#8217;m proposing to make flash drives secure, something Windows and Unix can&#8217;t do.  I&#8217;m proposing to eliminate autorun.inf files, boot sectors, and other common executables that can be written to by any other than the authorized distributor of the original code or a very limited set of agents authorized by same, and to run all other executables in extremely restrictive sandboxes.  Nothing complicated or &#8220;halting&#8221; about this at all.  It just happens to be radically different from how the Unix world and Microsoft currently do business.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://emergentchaos.com/archives/2008/12/eric-drexler-blogging.html/comment-page-1#comment-5303</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Sun, 14 Dec 2008 13:00:02 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2973#comment-5303</guid>
		<description>Nick,
At least my cell phone and camera have had additional software added despite the manufacturer&#039;s advice.  I know lots of people who adjust their car&#039;s software.
That you can list a small number of vectors by which viruses spread today does not mean that you can eliminate them all.  There have been viruses on every substantial -- and many insubstantial -- platforms.  Or are you proposing eliminating the &lt;s&gt;floppy disk&lt;/s&gt; USB key?
</description>
		<content:encoded><![CDATA[<p>Nick,<br />
At least my cell phone and camera have had additional software added despite the manufacturer&#8217;s advice.  I know lots of people who adjust their car&#8217;s software.<br />
That you can list a small number of vectors by which viruses spread today does not mean that you can eliminate them all.  There have been viruses on every substantial &#8212; and many insubstantial &#8212; platforms.  Or are you proposing eliminating the <s>floppy disk</s> USB key?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nick</title>
		<link>http://emergentchaos.com/archives/2008/12/eric-drexler-blogging.html/comment-page-1#comment-5302</link>
		<dc:creator>nick</dc:creator>
		<pubDate>Tue, 09 Dec 2008 21:19:44 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2973#comment-5302</guid>
		<description>&quot;You demonstrably can&#039;t make a useful computer which is immune from virus attack. The proof: a useful computer is one on which I can install software.&quot;
Well, no.  On the vast majority of useful computers users can&#039;t install new software.  Of course, marketing departments and consumers mostly do not call these &quot;computers&quot;, but instead cell phones, cameras, MP3 players, auto dashboards, etc. Not coincidentally, these work more reliably than computers on which users commonly install new software and are largely free of malware.
The vast majority of viruses spread via a very small number of vectors -- email attachments, web/Active X, autorun, and boot sector being prominent examples.   Eliminating these vectors in no way resembles the halting problem and is computationally a perfectly simple thing to do. These vectors were purposefully implemented by certain companies (ahem) because they made a value judgement that the added functionality was more important than the reduced reliability and security -- or because historically they were far more focused on the former than the latter.  But as I already indicated there are many more computers with far greater sales running on devices where a different judgment call was made.
There are a number of steps that could practically eliminate malware.  Chief among these is to separate data and executables, make executables write-once (and then only if properly signed by reputable code auditors) and then read-only, and run executables only in sandboxes with a very simple set of capabilities (as in capability-based security).  The problem is not Turing machines generally but the Von Neumann architecture in particular and with giving in to the demands of particular customers for convenience without sufficiently taking into account the problems of reliability and security that such specific functionality can create.
</description>
		<content:encoded><![CDATA[<p>&#8220;You demonstrably can&#8217;t make a useful computer which is immune from virus attack. The proof: a useful computer is one on which I can install software.&#8221;<br />
Well, no.  On the vast majority of useful computers users can&#8217;t install new software.  Of course, marketing departments and consumers mostly do not call these &#8220;computers&#8221;, but instead cell phones, cameras, MP3 players, auto dashboards, etc. Not coincidentally, these work more reliably than computers on which users commonly install new software and are largely free of malware.<br />
The vast majority of viruses spread via a very small number of vectors &#8212; email attachments, web/Active X, autorun, and boot sector being prominent examples.   Eliminating these vectors in no way resembles the halting problem and is computationally a perfectly simple thing to do. These vectors were purposefully implemented by certain companies (ahem) because they made a value judgement that the added functionality was more important than the reduced reliability and security &#8212; or because historically they were far more focused on the former than the latter.  But as I already indicated there are many more computers with far greater sales running on devices where a different judgment call was made.<br />
There are a number of steps that could practically eliminate malware.  Chief among these is to separate data and executables, make executables write-once (and then only if properly signed by reputable code auditors) and then read-only, and run executables only in sandboxes with a very simple set of capabilities (as in capability-based security).  The problem is not Turing machines generally but the Von Neumann architecture in particular and with giving in to the demands of particular customers for convenience without sufficiently taking into account the problems of reliability and security that such specific functionality can create.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://emergentchaos.com/archives/2008/12/eric-drexler-blogging.html/comment-page-1#comment-5301</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Tue, 09 Dec 2008 11:16:23 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2973#comment-5301</guid>
		<description>Radovan,
Horses may have wings.  But having never seen a horse with wings, I don&#039;t spend a lot of time worrying about them.  Similarly, I&#039;ve never seen a useful formal proof of usability (actually, I don&#039;t think I&#039;ve ever seen one at all).  I have seen experimentation show interesting things about systems for which usability was claimed.
Also, I did not entirely dismiss formal methods.  I wrote &quot;This is not to say that formal methods won&#039;t provide useful results on which we can build.&quot;  But they won&#039;t provide dramatic improvements.
</description>
		<content:encoded><![CDATA[<p>Radovan,<br />
Horses may have wings.  But having never seen a horse with wings, I don&#8217;t spend a lot of time worrying about them.  Similarly, I&#8217;ve never seen a useful formal proof of usability (actually, I don&#8217;t think I&#8217;ve ever seen one at all).  I have seen experimentation show interesting things about systems for which usability was claimed.<br />
Also, I did not entirely dismiss formal methods.  I wrote &#8220;This is not to say that formal methods won&#8217;t provide useful results on which we can build.&#8221;  But they won&#8217;t provide dramatic improvements.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Radovan Semancik</title>
		<link>http://emergentchaos.com/archives/2008/12/eric-drexler-blogging.html/comment-page-1#comment-5300</link>
		<dc:creator>Radovan Semancik</dc:creator>
		<pubDate>Tue, 09 Dec 2008 03:07:17 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2973#comment-5300</guid>
		<description>I do not share your white/black point of view. I can agree that formal proof of correctness is not a panacea and that it will not provide secure and usable system at the same time. Orange Book is a practical example, isn&#039;t it? The decision about the whole system will still be on the user, including security decisions. However, there is a big difference if user has no cue for the decision and if there are clear visual cues. For example a system that clearly warns user that he is probably doing something wrong will substantially add to the overall security. And a formal proof of this warning system may still be helpful.
And yes, practical system needs to be able to install software. However all the software may not come from the same source and may not run in the same security level. The way how current operating systems are implemented is far from ideal. I would not take that as an example of good (security) design. Yes, malicious code will still exists, but the goal of security is to make attack more costly than potential gain. And in current situation the virus attack costs almost nothing and the potential gain is enormous. We are on the highway to hell right now.
Any tool in security is just improving the situation. There is no panacea, no 100% security. I would not entirely dismiss formal methods. They have their place.
</description>
		<content:encoded><![CDATA[<p>I do not share your white/black point of view. I can agree that formal proof of correctness is not a panacea and that it will not provide secure and usable system at the same time. Orange Book is a practical example, isn&#8217;t it? The decision about the whole system will still be on the user, including security decisions. However, there is a big difference if user has no cue for the decision and if there are clear visual cues. For example a system that clearly warns user that he is probably doing something wrong will substantially add to the overall security. And a formal proof of this warning system may still be helpful.<br />
And yes, practical system needs to be able to install software. However all the software may not come from the same source and may not run in the same security level. The way how current operating systems are implemented is far from ideal. I would not take that as an example of good (security) design. Yes, malicious code will still exists, but the goal of security is to make attack more costly than potential gain. And in current situation the virus attack costs almost nothing and the potential gain is enormous. We are on the highway to hell right now.<br />
Any tool in security is just improving the situation. There is no panacea, no 100% security. I would not entirely dismiss formal methods. They have their place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Loomis</title>
		<link>http://emergentchaos.com/archives/2008/12/eric-drexler-blogging.html/comment-page-1#comment-5299</link>
		<dc:creator>Dean Loomis</dc:creator>
		<pubDate>Mon, 08 Dec 2008 19:42:57 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2973#comment-5299</guid>
		<description>Actually, Drexler is even more wrong than that.  Virus immunity doesn&#039;t depend on peoples&#039; gullibility, it&#039;s mathematically undecidable. First shown by Fred Cohen many years ago, any system that implements a universal Turing Machine (e.g. VBA in Microsoft Office)can support malicious code that is impossible to predict the existence of and prohibit in advance.
Sorry, the arms race between white hats and black hats is an eternal, immutable fact of nature.
</description>
		<content:encoded><![CDATA[<p>Actually, Drexler is even more wrong than that.  Virus immunity doesn&#8217;t depend on peoples&#8217; gullibility, it&#8217;s mathematically undecidable. First shown by Fred Cohen many years ago, any system that implements a universal Turing Machine (e.g. VBA in Microsoft Office)can support malicious code that is impossible to predict the existence of and prohibit in advance.<br />
Sorry, the arms race between white hats and black hats is an eternal, immutable fact of nature.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

