<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Disclosure</title>
	<atom:link href="http://blogs.law.harvard.edu/infolaw/2006/10/31/disclosure/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/infolaw/2006/10/31/disclosure/</link>
	<description>Information, Law, and the Law of Information</description>
	<lastBuildDate>Tue, 24 Nov 2009 00:08:14 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Derek Bambauer</title>
		<link>http://blogs.law.harvard.edu/infolaw/2006/10/31/disclosure/comment-page-1/#comment-1011</link>
		<dc:creator>Derek Bambauer</dc:creator>
		<pubDate>Fri, 03 Nov 2006 21:09:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2006/10/31/disclosure/#comment-1011</guid>
		<description>The difficult part here is determining when intermediate steps have been sufficiently played out.  How long does one give DHS to fix the problem?  (After all, don&#039;t Schneier and Schumer&#039;s warnings count here?)  Must one alert every federal agency?  Is this an &quot;exhaust all steps&quot; standard or a &quot;reasonable efforts&quot; standard? &lt;P&gt;These problems hold for most security problems. The difficulties are 1) absent public disclosure, there is often limited incentive to fix the problem (it&#039;s like catching spies - they shouldn&#039;t have been there in the first place, so one receives little credit for it), and 2) proof of concept is important, but revealing such things privately to government agencies may let them quash the report without fixing the problem. Intermediate steps are clearly important, and one should have to deal with this issue in mounting a necessity defense, but I think the risk here is that what we&#039;ve seen in the whistleblower context will be replicated in the security context...</description>
		<content:encoded><![CDATA[<p>The difficult part here is determining when intermediate steps have been sufficiently played out.  How long does one give DHS to fix the problem?  (After all, don&#8217;t Schneier and Schumer&#8217;s warnings count here?)  Must one alert every federal agency?  Is this an &#8220;exhaust all steps&#8221; standard or a &#8220;reasonable efforts&#8221; standard?
<p>These problems hold for most security problems. The difficulties are 1) absent public disclosure, there is often limited incentive to fix the problem (it&#8217;s like catching spies &#8211; they shouldn&#8217;t have been there in the first place, so one receives little credit for it), and 2) proof of concept is important, but revealing such things privately to government agencies may let them quash the report without fixing the problem. Intermediate steps are clearly important, and one should have to deal with this issue in mounting a necessity defense, but I think the risk here is that what we&#8217;ve seen in the whistleblower context will be replicated in the security context&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William McGeveran</title>
		<link>http://blogs.law.harvard.edu/infolaw/2006/10/31/disclosure/comment-page-1/#comment-960</link>
		<dc:creator>William McGeveran</dc:creator>
		<pubDate>Wed, 01 Nov 2006 19:57:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2006/10/31/disclosure/#comment-960</guid>
		<description>Becky, I agree with you.  As I said, &quot;There may be situations where you must show your audience what you are doing in order to make them believe you.&quot;  But I can imagine intermediate steps -- perhaps showing your tools to the Dept. of Homeland Security Inspector General -- that are still short of posting the tool on the web for other people to &lt;b&gt;duplicate&lt;/b&gt; your security breach.  Insofar as those alternatives are available, I think it should undermine the sort of defense Derek is proposing.</description>
		<content:encoded><![CDATA[<p>Becky, I agree with you.  As I said, &#8220;There may be situations where you must show your audience what you are doing in order to make them believe you.&#8221;  But I can imagine intermediate steps &#8212; perhaps showing your tools to the Dept. of Homeland Security Inspector General &#8212; that are still short of posting the tool on the web for other people to <b>duplicate</b> your security breach.  Insofar as those alternatives are available, I think it should undermine the sort of defense Derek is proposing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Becky</title>
		<link>http://blogs.law.harvard.edu/infolaw/2006/10/31/disclosure/comment-page-1/#comment-941</link>
		<dc:creator>Becky</dc:creator>
		<pubDate>Wed, 01 Nov 2006 13:27:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2006/10/31/disclosure/#comment-941</guid>
		<description>Excellent and interesting commentary Derek!  As far as Mr. McGeveran&#039;s comments above I have a question of practicality:  Would the government actually listen if Soghoian actually stated he could make the boarding passes?  How many citizens have warned/ commented/ suggested terrosim methods to the government and been ignored.  Maybe his method of drawing attention to the issue was the only reason the government gave it any attention.</description>
		<content:encoded><![CDATA[<p>Excellent and interesting commentary Derek!  As far as Mr. McGeveran&#8217;s comments above I have a question of practicality:  Would the government actually listen if Soghoian actually stated he could make the boarding passes?  How many citizens have warned/ commented/ suggested terrosim methods to the government and been ignored.  Maybe his method of drawing attention to the issue was the only reason the government gave it any attention.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neil Wehneman</title>
		<link>http://blogs.law.harvard.edu/infolaw/2006/10/31/disclosure/comment-page-1/#comment-938</link>
		<dc:creator>Neil Wehneman</dc:creator>
		<pubDate>Wed, 01 Nov 2006 03:21:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2006/10/31/disclosure/#comment-938</guid>
		<description>For those that are interested, I have recorded a twenty-minute &quot;lecture&quot; on the criminal law defense of necessity.  It&#039;s from the cases I studied and the notes I took in Criminal Law at Cincinnati.  (This is one episode of a larger project recording what I learned in law school.)

The specific episode on necessity is at &lt;a href=&quot;http://www.lifeofalawstudent.com/article.php?story=crimlaw24&quot; rel=&quot;nofollow&quot;&gt;http://www.lifeofalawstudent.com/article.php?story=crimlaw24.  It&#039;s licensed as CC-Attribution and GNU FDL.

 - Neil Wehneman</description>
		<content:encoded><![CDATA[<p>For those that are interested, I have recorded a twenty-minute &#8220;lecture&#8221; on the criminal law defense of necessity.  It&#8217;s from the cases I studied and the notes I took in Criminal Law at Cincinnati.  (This is one episode of a larger project recording what I learned in law school.)</p>
<p>The specific episode on necessity is at <a href="http://www.lifeofalawstudent.com/article.php?story=crimlaw24" rel="nofollow"></a><a href="http://www.lifeofalawstudent.com/article.php?story=crimlaw24" rel="nofollow">http://www.lifeofalawstudent.com/article.php?story=crimlaw24</a>.  It&#8217;s licensed as CC-Attribution and GNU FDL.</p>
<p> &#8211; Neil Wehneman</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William McGeveran</title>
		<link>http://blogs.law.harvard.edu/infolaw/2006/10/31/disclosure/comment-page-1/#comment-936</link>
		<dc:creator>William McGeveran</dc:creator>
		<pubDate>Tue, 31 Oct 2006 21:13:43 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2006/10/31/disclosure/#comment-936</guid>
		<description>Fascinating post, Derek!

I&#039;d suggest one possible expansion on the outlines of your suggested defense -- one that might make Soghoian&#039;s conduct out of bounds but still allow experts to raise the alarm about security breaches.

The harm in announcing to the world &quot;I can make fake boarding passes&quot; &lt;strong&gt;must&lt;/strong&gt; be less than the harm of then adding: &quot;And I am posting my tools on the web -- you can try it at home!&quot;  Did he (or should he) have a duty to limit himself to the first?

There may be situations where you must show your audience what you are doing in order to make them believe you.  And to be sure, there may still be some harm just in revealing the existence of a security loophole (perhaps outweighed, as you say, by disclosure increasing the likelihood that the loophole will be closed).  But, as we alreay know from the world of &quot;white hat&quot; hackers, there are good and bad ways of disclosing security flaws, and I might suggest that mass distribution of your tools falls into the &quot;bad&quot; category, and perhaps it should diqualify you from this line of defense -- however noble your intentions might have been.</description>
		<content:encoded><![CDATA[<p>Fascinating post, Derek!</p>
<p>I&#8217;d suggest one possible expansion on the outlines of your suggested defense &#8212; one that might make Soghoian&#8217;s conduct out of bounds but still allow experts to raise the alarm about security breaches.</p>
<p>The harm in announcing to the world &#8220;I can make fake boarding passes&#8221; <strong>must</strong> be less than the harm of then adding: &#8220;And I am posting my tools on the web &#8212; you can try it at home!&#8221;  Did he (or should he) have a duty to limit himself to the first?</p>
<p>There may be situations where you must show your audience what you are doing in order to make them believe you.  And to be sure, there may still be some harm just in revealing the existence of a security loophole (perhaps outweighed, as you say, by disclosure increasing the likelihood that the loophole will be closed).  But, as we alreay know from the world of &#8220;white hat&#8221; hackers, there are good and bad ways of disclosing security flaws, and I might suggest that mass distribution of your tools falls into the &#8220;bad&#8221; category, and perhaps it should diqualify you from this line of defense &#8212; however noble your intentions might have been.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
