<?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: Interview with Steven Murdoch on Finextra</title>
	<atom:link href="http://www.lightbluetouchpaper.org/2009/11/11/interview-with-steven-murdoch-on-finextra/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lightbluetouchpaper.org/2009/11/11/interview-with-steven-murdoch-on-finextra/</link>
	<description>Security Research, Computer Laboratory, University of Cambridge</description>
	<lastBuildDate>Fri, 10 Feb 2012 17:31:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Clive Robinson</title>
		<link>http://www.lightbluetouchpaper.org/2009/11/11/interview-with-steven-murdoch-on-finextra/comment-page-1/#comment-37928</link>
		<dc:creator>Clive Robinson</dc:creator>
		<pubDate>Fri, 13 Nov 2009 14:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/?p=1295#comment-37928</guid>
		<description>Steve,

Your face is getting seen all over the place, you&#039;ll be doing adverts next ;)

Protocols with public or private scrutiny do fail for a variety of reasons.

Unfortunatly a lot are designed on the backs of other protocols either for compatability or because the desigers patchwork their protocol together from other protocols.

As has recently been seen with TLS/SSL even longstanding protocols fail when used in a way that the original designers did not envisage.

Which was why I was surprised not to see &quot;fault analysis&quot; up on your list.

One of the reasons Chip-n-Spin got bad press (deservadly so) was the way the protocol fell back to mag stripe.

Arguably it was done for &quot;customer conveniance&quot;, which is the reason a lot of other security protocols fail (think expensive hotels where there is little or no checking when a person claims to be locked out of their room).

I expect to see a large number of privately developed protocols to fail to the desire for &quot;conveniance&quot; in a business not technicaly driven arena.</description>
		<content:encoded><![CDATA[<p>Steve,</p>
<p>Your face is getting seen all over the place, you&#8217;ll be doing adverts next <img src='http://www.lightbluetouchpaper.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>Protocols with public or private scrutiny do fail for a variety of reasons.</p>
<p>Unfortunatly a lot are designed on the backs of other protocols either for compatability or because the desigers patchwork their protocol together from other protocols.</p>
<p>As has recently been seen with TLS/SSL even longstanding protocols fail when used in a way that the original designers did not envisage.</p>
<p>Which was why I was surprised not to see &#8220;fault analysis&#8221; up on your list.</p>
<p>One of the reasons Chip-n-Spin got bad press (deservadly so) was the way the protocol fell back to mag stripe.</p>
<p>Arguably it was done for &#8220;customer conveniance&#8221;, which is the reason a lot of other security protocols fail (think expensive hotels where there is little or no checking when a person claims to be locked out of their room).</p>
<p>I expect to see a large number of privately developed protocols to fail to the desire for &#8220;conveniance&#8221; in a business not technicaly driven arena.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven J. Murdoch</title>
		<link>http://www.lightbluetouchpaper.org/2009/11/11/interview-with-steven-murdoch-on-finextra/comment-page-1/#comment-37835</link>
		<dc:creator>Steven J. Murdoch</dc:creator>
		<pubDate>Thu, 12 Nov 2009 12:18:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/?p=1295#comment-37835</guid>
		<description>@Sebastian

You are of course correct. What I was more thinking of is that there generally is a public RFC before widespread deployment of the protocol it implements.

I think the idea of &quot;running code&quot; is a very good one, and I&#039;d prefer if the IETF were even more strict about requiring multiple independent interoperable implementations than they currently are.

Not only is this good for improving the robustness of the protocol and clarity of the specification, it also encourages simplification. If the protocol designers need to build what they specify, unnecessary complication and risky corner-cases can be eliminated at an early stage.</description>
		<content:encoded><![CDATA[<p>@Sebastian</p>
<p>You are of course correct. What I was more thinking of is that there generally is a public RFC before widespread deployment of the protocol it implements.</p>
<p>I think the idea of &#8220;running code&#8221; is a very good one, and I&#8217;d prefer if the IETF were even more strict about requiring multiple independent interoperable implementations than they currently are.</p>
<p>Not only is this good for improving the robustness of the protocol and clarity of the specification, it also encourages simplification. If the protocol designers need to build what they specify, unnecessary complication and risky corner-cases can be eliminated at an early stage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sebastian</title>
		<link>http://www.lightbluetouchpaper.org/2009/11/11/interview-with-steven-murdoch-on-finextra/comment-page-1/#comment-37778</link>
		<dc:creator>Sebastian</dc:creator>
		<pubDate>Wed, 11 Nov 2009 23:41:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/?p=1295#comment-37778</guid>
		<description>Nice work Steven! Just one comment on the standardization of Internet protocols. You seem to suggest that there is always a specification before a protocol is implemented. In the IETF this is often the other way around. There exist public implementations of the protocol (&quot;running code&quot;) based on drafts even before the specification (the RFC) is made public. So experience with actual implementations feeds back into the standardisation process.</description>
		<content:encoded><![CDATA[<p>Nice work Steven! Just one comment on the standardization of Internet protocols. You seem to suggest that there is always a specification before a protocol is implemented. In the IETF this is often the other way around. There exist public implementations of the protocol (&#8220;running code&#8221;) based on drafts even before the specification (the RFC) is made public. So experience with actual implementations feeds back into the standardisation process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Feng Hao</title>
		<link>http://www.lightbluetouchpaper.org/2009/11/11/interview-with-steven-murdoch-on-finextra/comment-page-1/#comment-37753</link>
		<dc:creator>Feng Hao</dc:creator>
		<pubDate>Wed, 11 Nov 2009 19:26:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/?p=1295#comment-37753</guid>
		<description>I like your comment on &quot;simplicity&quot;. That&#039;s spot-on. In the protocol design, people often like to make it unnecessarily complex as they think a complex protocol looks more impressive. But complexity invites all sorts of attacks.

Nice work (and also Kudos to Saar), though I&#039;m not less sure whether there are still banks willing to issue new cards with the name &quot;S.J. Murdoch&quot; on :)</description>
		<content:encoded><![CDATA[<p>I like your comment on &#8220;simplicity&#8221;. That&#8217;s spot-on. In the protocol design, people often like to make it unnecessarily complex as they think a complex protocol looks more impressive. But complexity invites all sorts of attacks.</p>
<p>Nice work (and also Kudos to Saar), though I&#8217;m not less sure whether there are still banks willing to issue new cards with the name &#8220;S.J. Murdoch&#8221; on <img src='http://www.lightbluetouchpaper.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

