<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Dustin D. Trammell</title>
	<atom:link href="http://blog.dustintrammell.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dustintrammell.com</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 21:10:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on ToorCon Seattle (Beta) by Laurentino</title>
		<link>http://blog.dustintrammell.com/2007/05/16/toorcon-seattle-beta/#comment-1333</link>
		<dc:creator><![CDATA[Laurentino]]></dc:creator>
		<pubDate>Fri, 10 Feb 2012 21:10:11 +0000</pubDate>
		<guid isPermaLink="false">http://dtrammell.wordpress.com/2007/05/16/toorcon-seattle-beta/#comment-1333</guid>
		<description><![CDATA[i went in 2008, and while it was ok, didn&#8217;t get any pualicatrr OMG moments that made me want to go this year. it seems most of the speakers ended to present their folio of past work, from university to current, which got tedious after several speakers. the most impressive ones focused on smaller areas of their careers, pualicatrr jobs and clients Reply]]></description>
		<content:encoded><![CDATA[<p>i went in 2008, and while it was ok, didn&#8217;t get any pualicatrr OMG moments that made me want to go this year. it seems most of the speakers ended to present their folio of past work, from university to current, which got tedious after several speakers. the most impressive ones focused on smaller areas of their careers, pualicatrr jobs and clients Reply</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Metroid Security Mechanism by TJ Leeland</title>
		<link>http://blog.dustintrammell.com/2007/11/16/metroid-security-mechanism/#comment-1312</link>
		<dc:creator><![CDATA[TJ Leeland]]></dc:creator>
		<pubDate>Wed, 09 Feb 2011 16:33:33 +0000</pubDate>
		<guid isPermaLink="false">http://dtrammell.wordpress.com/2007/11/16/metroid-security-mechanism/#comment-1312</guid>
		<description><![CDATA[as security expert I can tell you why make-believe security is better than real life: make-believe users don&#039;t call tech-support.

Seriously.

The more secure you make things, the more calls you get from users who can&#039;t get into their systems. You add &quot;random&quot; anything to a login process and you will see lockouts skyrocket and calls to support will jump along with it. It&#039;s always a balance between security and usability. They can only give you the level of security the dumbest users can handle.]]></description>
		<content:encoded><![CDATA[<p>as security expert I can tell you why make-believe security is better than real life: make-believe users don&#8217;t call tech-support.</p>
<p>Seriously.</p>
<p>The more secure you make things, the more calls you get from users who can&#8217;t get into their systems. You add &#8220;random&#8221; anything to a login process and you will see lockouts skyrocket and calls to support will jump along with it. It&#8217;s always a balance between security and usability. They can only give you the level of security the dumbest users can handle.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cleverbot Not So Clever by CR</title>
		<link>http://blog.dustintrammell.com/2009/12/29/cleverbot-not-so-clever/#comment-1153</link>
		<dc:creator><![CDATA[CR]]></dc:creator>
		<pubDate>Tue, 30 Nov 2010 20:01:27 +0000</pubDate>
		<guid isPermaLink="false">http://dtrammell.wordpress.com/?p=242#comment-1153</guid>
		<description><![CDATA[I think you would find this website very funny:

http://www.notsocleverbot.com

My personal favorite:

User: Hey there!
Cleverbot: How are you?
User: Pretty good.
Cleverbot: That&#039;s good.
User: You see the new Twilight Movie?
Cleverbot: I&#039;m not interested in any of the twilight movies or books.
User: You&#039;re not into vampires?
Cleverbot: I&#039;m not into humans]]></description>
		<content:encoded><![CDATA[<p>I think you would find this website very funny:</p>
<p><a href="http://www.notsocleverbot.com" rel="nofollow">http://www.notsocleverbot.com</a></p>
<p>My personal favorite:</p>
<p>User: Hey there!<br />
Cleverbot: How are you?<br />
User: Pretty good.<br />
Cleverbot: That&#8217;s good.<br />
User: You see the new Twilight Movie?<br />
Cleverbot: I&#8217;m not interested in any of the twilight movies or books.<br />
User: You&#8217;re not into vampires?<br />
Cleverbot: I&#8217;m not into humans</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Four-factor Authentication by Ted Bigham</title>
		<link>http://blog.dustintrammell.com/2008/11/21/four-factor-authentication/#comment-1074</link>
		<dc:creator><![CDATA[Ted Bigham]]></dc:creator>
		<pubDate>Sat, 09 Oct 2010 09:24:30 +0000</pubDate>
		<guid isPermaLink="false">http://dtrammell.wordpress.com/?p=160#comment-1074</guid>
		<description><![CDATA[I never said foolproof.  If someone tortures your password from you, then that factor is compromised; all the reason for more than one. I also never said the &quot;data&quot; for each factor is self identifying.  If your pin number is 1234, that is not unique, but is secret and qualifies as a factor when associated with your id or card number (which is not secret and not a factor). A location is a valid point of reference especially on the fraud prevention realm, but is not a factor of identifying a person.  Any person can be at that location claiming to be you, just like any person can say they their pin is 1234 claiming to be you. The differenece is that location is not secret.]]></description>
		<content:encoded><![CDATA[<p>I never said foolproof.  If someone tortures your password from you, then that factor is compromised; all the reason for more than one. I also never said the &#8220;data&#8221; for each factor is self identifying.  If your pin number is 1234, that is not unique, but is secret and qualifies as a factor when associated with your id or card number (which is not secret and not a factor). A location is a valid point of reference especially on the fraud prevention realm, but is not a factor of identifying a person.  Any person can be at that location claiming to be you, just like any person can say they their pin is 1234 claiming to be you. The differenece is that location is not secret.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SmartPhone Unlock Screens: Moving in the Wrong Direction by Judson Dicampli</title>
		<link>http://blog.dustintrammell.com/2009/11/10/smartphone-unlock-screens-moving-in-the-wrong-direction/#comment-1060</link>
		<dc:creator><![CDATA[Judson Dicampli]]></dc:creator>
		<pubDate>Mon, 16 Aug 2010 12:29:01 +0000</pubDate>
		<guid isPermaLink="false">http://dtrammell.wordpress.com/?p=235#comment-1060</guid>
		<description><![CDATA[Whilst I really like a physical keyboard, after managing the Samsung Captivate for about 15 minutes, it&#039;s hard to move back. At the moment I am debating whether to go to Verizon for the Droid X, move to Dash for the EVO, or stay with AT&amp;T for the Captivate...selections, decisions.]]></description>
		<content:encoded><![CDATA[<p>Whilst I really like a physical keyboard, after managing the Samsung Captivate for about 15 minutes, it&#8217;s hard to move back. At the moment I am debating whether to go to Verizon for the Droid X, move to Dash for the EVO, or stay with AT&amp;T for the Captivate&#8230;selections, decisions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Four-factor Authentication by Travis H.</title>
		<link>http://blog.dustintrammell.com/2008/11/21/four-factor-authentication/#comment-1048</link>
		<dc:creator><![CDATA[Travis H.]]></dc:creator>
		<pubDate>Tue, 15 Jun 2010 11:10:12 +0000</pubDate>
		<guid isPermaLink="false">http://dtrammell.wordpress.com/?p=160#comment-1048</guid>
		<description><![CDATA[Re: Ted Bigham and Joat

Disagree.  Nobody says that a factor of authentication has to be foolproof, only identifying one person.  In fact, if it did, we would never need two-factor authentication!  By the same argument, &quot;something you know&quot; isn&#039;t good because someone could torture it out of you, and &quot;something you have&quot; isn&#039;t sufficient since it could be stolen or duplicated.

&quot;Where you are&quot; can also be important in situations like IFF devices, since not only do we want to know that the responder is friendly, we want to know that the challenge-response is not being proxied to a friendly at a distant location (though they don&#039;t necessarily use that in IFF devices).

I&#039;m actually getting a fair number of hits from this site, so I figured I&#039;d share an updated URL:

http://www.subspacefield.org/security/security_concepts.html

Search for &quot;Authentication Factors&quot; to find the section on five-factor authentication; right now it is S11.8.

I don&#039;t discuss this, but it&#039;s worth noting that some of these authentication factors are only useful in certain circumstances.  For example, the biometric authentication isn&#039;t always useful in network security, because the adversary could simply replay a recorded biometric signature; one has no proof that one is actually getting a reading from trusted biometric equipment, unless one engages in what TCPA calls &quot;Remote Attestation&quot;.  If one isn&#039;t sure where one is getting the reading from, then it&#039;s just a string of bits, and so it&#039;s effectively &quot;something you know&quot;.]]></description>
		<content:encoded><![CDATA[<p>Re: Ted Bigham and Joat</p>
<p>Disagree.  Nobody says that a factor of authentication has to be foolproof, only identifying one person.  In fact, if it did, we would never need two-factor authentication!  By the same argument, &#8220;something you know&#8221; isn&#8217;t good because someone could torture it out of you, and &#8220;something you have&#8221; isn&#8217;t sufficient since it could be stolen or duplicated.</p>
<p>&#8220;Where you are&#8221; can also be important in situations like IFF devices, since not only do we want to know that the responder is friendly, we want to know that the challenge-response is not being proxied to a friendly at a distant location (though they don&#8217;t necessarily use that in IFF devices).</p>
<p>I&#8217;m actually getting a fair number of hits from this site, so I figured I&#8217;d share an updated URL:</p>
<p><a href="http://www.subspacefield.org/security/security_concepts.html" rel="nofollow">http://www.subspacefield.org/security/security_concepts.html</a></p>
<p>Search for &#8220;Authentication Factors&#8221; to find the section on five-factor authentication; right now it is S11.8.</p>
<p>I don&#8217;t discuss this, but it&#8217;s worth noting that some of these authentication factors are only useful in certain circumstances.  For example, the biometric authentication isn&#8217;t always useful in network security, because the adversary could simply replay a recorded biometric signature; one has no proof that one is actually getting a reading from trusted biometric equipment, unless one engages in what TCPA calls &#8220;Remote Attestation&#8221;.  If one isn&#8217;t sure where one is getting the reading from, then it&#8217;s just a string of bits, and so it&#8217;s effectively &#8220;something you know&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Advanced Persistent Threat by Brandon Dixon</title>
		<link>http://blog.dustintrammell.com/2010/04/12/advanced-persistent-threat/#comment-1028</link>
		<dc:creator><![CDATA[Brandon Dixon]]></dc:creator>
		<pubDate>Thu, 20 May 2010 19:04:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dustintrammell.com/?p=271#comment-1028</guid>
		<description><![CDATA[I thought I may have been the only one to share the same thought. It&#039;s gotten worse than cloud computing. I am pretty certain I have heard those 3 letters more than anything in the past few months. Whitepapers, blogs, tweets...make it stop!]]></description>
		<content:encoded><![CDATA[<p>I thought I may have been the only one to share the same thought. It&#8217;s gotten worse than cloud computing. I am pretty certain I have heard those 3 letters more than anything in the past few months. Whitepapers, blogs, tweets&#8230;make it stop!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Four-factor Authentication by Ted Bigham</title>
		<link>http://blog.dustintrammell.com/2008/11/21/four-factor-authentication/#comment-1038</link>
		<dc:creator><![CDATA[Ted Bigham]]></dc:creator>
		<pubDate>Thu, 20 May 2010 19:03:27 +0000</pubDate>
		<guid isPermaLink="false">http://dtrammell.wordpress.com/?p=160#comment-1038</guid>
		<description><![CDATA[In fear of repeating what joat said, &quot;where you are&quot; is not a factor of authentication.  It fails the first requirement to be factor, which is that it must work as a &quot;single factor&quot; authentication mechanism.  Simply knowing the location where someone is accessing a system from is rarely enough to authenticate them.

For example, if I walk up to a coworker&#039;s computer while they are away, a &quot;where you are&quot; auth mechanism would let me log in by simply entering their login name.  This is obviously not secure.  Any location can hold more than one person at different times.  The type of place that &quot;where you are&quot; authentication would be valid is something like a prison cell, where you know for a fact that only a certain person can be in that place at the time of authentication.

Another reason most (is not all) forms of &quot;where you are&quot; authentication don&#039;t qualify as factors, is because they tend to depend on one of the other factors.  This also disqualifies it.  An example would be ordering room service from your hotel room.  Although the front desk can tell exactly where the phone call is coming from, the room itself is only secured by a key (something you have).  So if someone compromises your room key, they have also compromised your location.  The mechanisms need to be independent of each other.

There are still only &quot;three&quot; factors for authentication.  Four is just marketing.]]></description>
		<content:encoded><![CDATA[<p>In fear of repeating what joat said, &#8220;where you are&#8221; is not a factor of authentication.  It fails the first requirement to be factor, which is that it must work as a &#8220;single factor&#8221; authentication mechanism.  Simply knowing the location where someone is accessing a system from is rarely enough to authenticate them.</p>
<p>For example, if I walk up to a coworker&#8217;s computer while they are away, a &#8220;where you are&#8221; auth mechanism would let me log in by simply entering their login name.  This is obviously not secure.  Any location can hold more than one person at different times.  The type of place that &#8220;where you are&#8221; authentication would be valid is something like a prison cell, where you know for a fact that only a certain person can be in that place at the time of authentication.</p>
<p>Another reason most (is not all) forms of &#8220;where you are&#8221; authentication don&#8217;t qualify as factors, is because they tend to depend on one of the other factors.  This also disqualifies it.  An example would be ordering room service from your hotel room.  Although the front desk can tell exactly where the phone call is coming from, the room itself is only secured by a key (something you have).  So if someone compromises your room key, they have also compromised your location.  The mechanisms need to be independent of each other.</p>
<p>There are still only &#8220;three&#8221; factors for authentication.  Four is just marketing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cleverbot Not So Clever by Little Professor</title>
		<link>http://blog.dustintrammell.com/2009/12/29/cleverbot-not-so-clever/#comment-1046</link>
		<dc:creator><![CDATA[Little Professor]]></dc:creator>
		<pubDate>Thu, 20 May 2010 19:02:31 +0000</pubDate>
		<guid isPermaLink="false">http://dtrammell.wordpress.com/?p=242#comment-1046</guid>
		<description><![CDATA[I think I know why Cleverbot always says, “I’m not Cleverbot. You are!”. I think it’s because Cleverbot learns from people, and people always call it Cleverbot. Any time it says, “Hi, Cleverbot”, you say, “I’m not Cleverbot. You are!”, so it thinks that that is the correct reply to “Hi, Cleverbot”.]]></description>
		<content:encoded><![CDATA[<p>I think I know why Cleverbot always says, “I’m not Cleverbot. You are!”. I think it’s because Cleverbot learns from people, and people always call it Cleverbot. Any time it says, “Hi, Cleverbot”, you say, “I’m not Cleverbot. You are!”, so it thinks that that is the correct reply to “Hi, Cleverbot”.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Metroid Security Mechanism by SmartPhone Unlock Screens: Moving in the Wrong Direction &#171; Dustin D. Trammell</title>
		<link>http://blog.dustintrammell.com/2007/11/16/metroid-security-mechanism/#comment-1013</link>
		<dc:creator><![CDATA[SmartPhone Unlock Screens: Moving in the Wrong Direction &#171; Dustin D. Trammell]]></dc:creator>
		<pubDate>Tue, 10 Nov 2009 22:28:22 +0000</pubDate>
		<guid isPermaLink="false">http://dtrammell.wordpress.com/2007/11/16/metroid-security-mechanism/#comment-1013</guid>
		<description><![CDATA[[...] Needless to say, I tend to wipe my phone&#8217;s touch-screen quite frequently.  Why hasn&#8217;t anyone implemented a lock screen that uses a technique like this one? [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Needless to say, I tend to wipe my phone&#8217;s touch-screen quite frequently.  Why hasn&#8217;t anyone implemented a lock screen that uses a technique like this one? [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

