<?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: Think Hoarding Passwords Keeps You Safe From Firing? Think Again (Forbes Cross-Post)	</title>
	<atom:link href="https://blog.ericgoldman.org/archives/2013/11/think-hoarding-passwords-keeps-you-safe-from-firing-think-again-forbes-cross-post.htm/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.ericgoldman.org/archives/2013/11/think-hoarding-passwords-keeps-you-safe-from-firing-think-again-forbes-cross-post.htm</link>
	<description></description>
	<lastBuildDate>Mon, 11 Nov 2013 22:46:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: btjunkie		</title>
		<link>https://blog.ericgoldman.org/archives/2013/11/think-hoarding-passwords-keeps-you-safe-from-firing-think-again-forbes-cross-post.htm#comment-632</link>

		<dc:creator><![CDATA[btjunkie]]></dc:creator>
		<pubDate>Mon, 11 Nov 2013 22:46:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=11074#comment-632</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blog.ericgoldman.org/archives/2013/11/think-hoarding-passwords-keeps-you-safe-from-firing-think-again-forbes-cross-post.htm#comment-631&quot;&gt;Eric Goldman&lt;/a&gt;.

Thanks Eric. I&#039;ll have to read it this evening. Love the blog by the way.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blog.ericgoldman.org/archives/2013/11/think-hoarding-passwords-keeps-you-safe-from-firing-think-again-forbes-cross-post.htm#comment-631">Eric Goldman</a>.</p>
<p>Thanks Eric. I&#8217;ll have to read it this evening. Love the blog by the way.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Eric Goldman		</title>
		<link>https://blog.ericgoldman.org/archives/2013/11/think-hoarding-passwords-keeps-you-safe-from-firing-think-again-forbes-cross-post.htm#comment-631</link>

		<dc:creator><![CDATA[Eric Goldman]]></dc:creator>
		<pubDate>Mon, 11 Nov 2013 22:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=11074#comment-631</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://blog.ericgoldman.org/archives/2013/11/think-hoarding-passwords-keeps-you-safe-from-firing-think-again-forbes-cross-post.htm#comment-630&quot;&gt;btjunkie&lt;/a&gt;.

The court&#039;s opinion goes into a lot of detail about this issue, so I encourage you to read it.  I didn&#039;t understand all of the details, but it sounded like Childs did a good job erecting some barriers.  Eric.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://blog.ericgoldman.org/archives/2013/11/think-hoarding-passwords-keeps-you-safe-from-firing-think-again-forbes-cross-post.htm#comment-630">btjunkie</a>.</p>
<p>The court&#8217;s opinion goes into a lot of detail about this issue, so I encourage you to read it.  I didn&#8217;t understand all of the details, but it sounded like Childs did a good job erecting some barriers.  Eric.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: btjunkie		</title>
		<link>https://blog.ericgoldman.org/archives/2013/11/think-hoarding-passwords-keeps-you-safe-from-firing-think-again-forbes-cross-post.htm#comment-630</link>

		<dc:creator><![CDATA[btjunkie]]></dc:creator>
		<pubDate>Mon, 11 Nov 2013 21:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ericgoldman.org/?p=11074#comment-630</guid>

					<description><![CDATA[I&#039;m pretty curious about this part: &quot;deliberately configured that system so that no one else could access it,
 set it up so that anyone other than him attempting to enter it would 
erase the data stored in it&quot;


I&#039;m a network engineer and I can say for certain that the vast majority of network devices--actually EVERY network device that I know of--can have the password reset. The password reset process is usually intrusive. Most devices have to be rebooted, for example, but I&#039;ve never heard of a network device that will erase itself if someone tries to reset the password.


I&#039;m guessing what he actually did was store the passwords in a secure vault like Keepass and then refuse to hand over the master key to it. Secure password vaults can easily be configured to delete themselves after a certain number of failures.


What he did was definitely wrong and they were right to prosecute him, but the accusation still rings of hyperbole. I don&#039;t see how they could have been completely locked out of their network by what he did. If anyone knows the details please reply. I&#039;m genuinely curious.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m pretty curious about this part: &#8220;deliberately configured that system so that no one else could access it,<br />
 set it up so that anyone other than him attempting to enter it would<br />
erase the data stored in it&#8221;</p>
<p>I&#8217;m a network engineer and I can say for certain that the vast majority of network devices&#8211;actually EVERY network device that I know of&#8211;can have the password reset. The password reset process is usually intrusive. Most devices have to be rebooted, for example, but I&#8217;ve never heard of a network device that will erase itself if someone tries to reset the password.</p>
<p>I&#8217;m guessing what he actually did was store the passwords in a secure vault like Keepass and then refuse to hand over the master key to it. Secure password vaults can easily be configured to delete themselves after a certain number of failures.</p>
<p>What he did was definitely wrong and they were right to prosecute him, but the accusation still rings of hyperbole. I don&#8217;t see how they could have been completely locked out of their network by what he did. If anyone knows the details please reply. I&#8217;m genuinely curious.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
