<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: When End-to-End Encryption is really not End-to-End.</title>
	<atom:link href="http://www.paymentsystemsblog.com/2009/01/20/when-end-to-end-encryption-is-really-not-end-to-end/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.paymentsystemsblog.com/2009/01/20/when-end-to-end-encryption-is-really-not-end-to-end/</link>
	<description>David D. Bergert</description>
	<lastBuildDate>Sun, 11 Apr 2010 04:11:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Timothy Johnson</title>
		<link>http://www.paymentsystemsblog.com/2009/01/20/when-end-to-end-encryption-is-really-not-end-to-end/comment-page-1/#comment-1057</link>
		<dc:creator>Timothy Johnson</dc:creator>
		<pubDate>Mon, 23 Mar 2009 17:29:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.paymentsystemsblog.com/2009/01/20/when-end-to-end-encryption-is-really-not-end-to-end/#comment-1057</guid>
		<description>DISCLOSURE: My company provides encryption technology for the diagram above.  Your PowerPoint demonstrates Where we encrypt Layer @ 2,3, and 4.</description>
		<content:encoded><![CDATA[<p>DISCLOSURE: My company provides encryption technology for the diagram above.  Your PowerPoint demonstrates Where we encrypt Layer @ 2,3, and 4.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Hazel</title>
		<link>http://www.paymentsystemsblog.com/2009/01/20/when-end-to-end-encryption-is-really-not-end-to-end/comment-page-1/#comment-861</link>
		<dc:creator>Patrick Hazel</dc:creator>
		<pubDate>Fri, 23 Jan 2009 17:54:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.paymentsystemsblog.com/2009/01/20/when-end-to-end-encryption-is-really-not-end-to-end/#comment-861</guid>
		<description>End to end encryption, as you properly define it, has been commercially deployed in the US.  The underlying crypto uses what is called &quot;format preserving encryption&quot; and uses either Triple DES or AES.  In the US, VeriFone has deployed this in a product they call &quot;VSP&quot;. I would strongly emphasize your point as well that most &quot;end to end&quot; encryption claims wilt under qualified review.  DISCLOSURE: My company provides the crypto and supporting systems to VeriFone so be aware of my bias.</description>
		<content:encoded><![CDATA[<p>End to end encryption, as you properly define it, has been commercially deployed in the US.  The underlying crypto uses what is called &#8220;format preserving encryption&#8221; and uses either Triple DES or AES.  In the US, VeriFone has deployed this in a product they call &#8220;VSP&#8221;. I would strongly emphasize your point as well that most &#8220;end to end&#8221; encryption claims wilt under qualified review.  DISCLOSURE: My company provides the crypto and supporting systems to VeriFone so be aware of my bias.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heartland Payment Systems Breach - My Thoughts &#124; Payment Systems Blog</title>
		<link>http://www.paymentsystemsblog.com/2009/01/20/when-end-to-end-encryption-is-really-not-end-to-end/comment-page-1/#comment-847</link>
		<dc:creator>Heartland Payment Systems Breach - My Thoughts &#124; Payment Systems Blog</dc:creator>
		<pubDate>Wed, 21 Jan 2009 15:24:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.paymentsystemsblog.com/2009/01/20/when-end-to-end-encryption-is-really-not-end-to-end/#comment-847</guid>
		<description>[...] And lastly End-to-End Encryption solutions would not of prevented this either: see my post here: When End-to-End Encryption is really not End-to-End. No TweetBacks yet. (Be the first to Tweet this post) Possibly Related Posts (automatically [...]</description>
		<content:encoded><![CDATA[<p>[...] And lastly End-to-End Encryption solutions would not of prevented this either: see my post here: When End-to-End Encryption is really not End-to-End. No TweetBacks yet. (Be the first to Tweet this post) Possibly Related Posts (automatically [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
