<?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 on: Gmail S/MIME</title>
	<atom:link href="http://agilityloop.com/2009/04/16/gmail-smime/feed/" rel="self" type="application/rss+xml" />
	<link>http://agilityloop.com/2009/04/16/gmail-smime/</link>
	<description>The musings of the agile on the world of tech and government</description>
	<lastBuildDate>Thu, 26 Aug 2010 19:39:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Peter Hesse</title>
		<link>http://agilityloop.com/2009/04/16/gmail-smime/#comment-4</link>
		<dc:creator>Peter Hesse</dc:creator>
		<pubDate>Fri, 17 Apr 2009 13:45:57 +0000</pubDate>
		<guid isPermaLink="false">http://agilityloop.wordpress.com/?p=11#comment-4</guid>
		<description>Kevin, thanks for the link and glad you enjoy the blog.

Tim, the biggest problem with encryption/signatures in webmail apps is the fact that the webmail provider generally can&#039;t/shouldn&#039;t be trusted with your private key, or even the secured message. At a minimum, you need some interaction between a private key held on the client side (or through secure network storage) and the email message.

It really shouldn&#039;t be hard, and I would be more than happy to help any of the big webmail providers integrate it.  The webmail provider would need to understand and process the S/MIME, and just call back to the holder of the private key when the signature or decryption is necessary.

Microsoft&#039;s Outlook Web Access has supported since Exchange 2007. However that&#039;s not a general-purpose webmail provider, but is a web-based email application.</description>
		<content:encoded><![CDATA[<p>Kevin, thanks for the link and glad you enjoy the blog.</p>
<p>Tim, the biggest problem with encryption/signatures in webmail apps is the fact that the webmail provider generally can&#8217;t/shouldn&#8217;t be trusted with your private key, or even the secured message. At a minimum, you need some interaction between a private key held on the client side (or through secure network storage) and the email message.</p>
<p>It really shouldn&#8217;t be hard, and I would be more than happy to help any of the big webmail providers integrate it.  The webmail provider would need to understand and process the S/MIME, and just call back to the holder of the private key when the signature or decryption is necessary.</p>
<p>Microsoft&#8217;s Outlook Web Access has supported since Exchange 2007. However that&#8217;s not a general-purpose webmail provider, but is a web-based email application.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tim</title>
		<link>http://agilityloop.com/2009/04/16/gmail-smime/#comment-3</link>
		<dc:creator>tim</dc:creator>
		<pubDate>Fri, 17 Apr 2009 03:15:47 +0000</pubDate>
		<guid isPermaLink="false">http://agilityloop.wordpress.com/?p=11#comment-3</guid>
		<description>I&#039;d like to talk to a programmer, or maybe just do a little googling, to find out why it&#039;s difficult to add signatures and encryption to webmail apps.  doesn&#039;t seem like it should be that hard.  and if it&#039;s in fact not difficult to do, why the delay in adoption?  this was a killer on my last PKI project...end users all used webmail (hotmail, yahoo, etc) and couldn&#039;t digitally sign messages such as revocation and renewal requests, which resulted in a ton of help desk support being required.</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to talk to a programmer, or maybe just do a little googling, to find out why it&#8217;s difficult to add signatures and encryption to webmail apps.  doesn&#8217;t seem like it should be that hard.  and if it&#8217;s in fact not difficult to do, why the delay in adoption?  this was a killer on my last PKI project&#8230;end users all used webmail (hotmail, yahoo, etc) and couldn&#8217;t digitally sign messages such as revocation and renewal requests, which resulted in a ton of help desk support being required.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
