<?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: Automatically Exchanging Encryption Keys</title>
	<atom:link href="http://stealthisidea.com/articles/exchanging-public-keys/feed/" rel="self" type="application/rss+xml" />
	<link>http://stealthisidea.com/articles/exchanging-public-keys/</link>
	<description>Philip Haine&#039;s articles on Product Vision, Innovation and Design</description>
	<lastBuildDate>Tue, 06 Dec 2011 23:38:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: edwinh</title>
		<link>http://stealthisidea.com/articles/exchanging-public-keys/comment-page-1/#comment-2123</link>
		<dc:creator>edwinh</dc:creator>
		<pubDate>Sat, 12 May 2007 18:35:01 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/articles/exchanging-public-keys/#comment-2123</guid>
		<description>Forcing employees to send and receive only encrypted mails would be troublesome. 

The sales people would raise high holy hell if their customers and especially their prospects could not email them without encryption. Same thing for customer support people. 

What about all the automated emails that get sent from various systems and servers being run internally? Many of these servers are software bought from a 3rd party and the company cannot easily modify them to send encrypted mails.

So while I agree that encrypted mails are a good idea for companies, it is not feasible to mandate encryption.

Also, another idea on the way public keys should be traded is a DNS-like lookup system for public keys. Once a certificate authority provides a public key to an email address, this key would be shared and forwarded amongst all the authorities in the same way that a domain name is shared and forwarded amongst DNS servers. To go along with this, a new type of key lookup server would be implemented. This server could be run by the certificate authorities, ISPs, or even particular techie people on their linux box at home. The final piece is that email client software should be able to look up any email address to on this server to see if there is a public key registered for it. If so, it can use it for encryption. The user should even be given the choice of whether to use this key automatically when sending emails in order to encrypt them whenever possible. 

As more and more people sign up for encryption, this type of system will become more and more useful.

Someone please write a standard for this!</description>
		<content:encoded><![CDATA[<p>Forcing employees to send and receive only encrypted mails would be troublesome. </p>
<p>The sales people would raise high holy hell if their customers and especially their prospects could not email them without encryption. Same thing for customer support people. </p>
<p>What about all the automated emails that get sent from various systems and servers being run internally? Many of these servers are software bought from a 3rd party and the company cannot easily modify them to send encrypted mails.</p>
<p>So while I agree that encrypted mails are a good idea for companies, it is not feasible to mandate encryption.</p>
<p>Also, another idea on the way public keys should be traded is a DNS-like lookup system for public keys. Once a certificate authority provides a public key to an email address, this key would be shared and forwarded amongst all the authorities in the same way that a domain name is shared and forwarded amongst DNS servers. To go along with this, a new type of key lookup server would be implemented. This server could be run by the certificate authorities, ISPs, or even particular techie people on their linux box at home. The final piece is that email client software should be able to look up any email address to on this server to see if there is a public key registered for it. If so, it can use it for encryption. The user should even be given the choice of whether to use this key automatically when sending emails in order to encrypt them whenever possible. </p>
<p>As more and more people sign up for encryption, this type of system will become more and more useful.</p>
<p>Someone please write a standard for this!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

