<?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: Keeping your email secure</title>
	<atom:link href="http://it.gen.nz/2008/07/24/keeping-your-email-secure/feed/" rel="self" type="application/rss+xml" />
	<link>http://it.gen.nz/2008/07/24/keeping-your-email-secure/</link>
	<description>Writings on technology and society from Wellington, New Zealand</description>
	<lastBuildDate>Wed, 08 Feb 2012 04:57:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: colin</title>
		<link>http://it.gen.nz/2008/07/24/keeping-your-email-secure/comment-page-1/#comment-706</link>
		<dc:creator>colin</dc:creator>
		<pubDate>Tue, 29 Jul 2008 19:25:43 +0000</pubDate>
		<guid isPermaLink="false">http://it.gen.nz/?p=130#comment-706</guid>
		<description>Decent crypto can indeed protect email contents from most eavesdroppers - but it&#039;s generally hard to use (compared to email without crypto) and doesn&#039;t play well with corporate email systems. Yes, you can provide smart cards with keys on to users but most people won&#039;t use them. Crypto right to the desktop is hard to use.

The public service has been running a crypto layer on everyday email for years. It&#039;s completely transparent to the end users. It works through the various departments&#039; mail servers recognising each other and encrypting all traffic between them automatically. Crypto is only applied during the transit across the Internet; not down to the desktop. Users are barely aware of the system. This works well - but it wouldn&#039;t have solved the National Party&#039;s problem - even if they used this system - unless their emails were leaked as a result of eavesdropping while they were being transmitted across the open Internet.

In the National Party case the journalist concerned has said several times that he was given the emails by someone with a right to have them. Crypto won&#039;t fix that.</description>
		<content:encoded><![CDATA[<p>Decent crypto can indeed protect email contents from most eavesdroppers &#8211; but it&#8217;s generally hard to use (compared to email without crypto) and doesn&#8217;t play well with corporate email systems. Yes, you can provide smart cards with keys on to users but most people won&#8217;t use them. Crypto right to the desktop is hard to use.</p>
<p>The public service has been running a crypto layer on everyday email for years. It&#8217;s completely transparent to the end users. It works through the various departments&#8217; mail servers recognising each other and encrypting all traffic between them automatically. Crypto is only applied during the transit across the Internet; not down to the desktop. Users are barely aware of the system. This works well &#8211; but it wouldn&#8217;t have solved the National Party&#8217;s problem &#8211; even if they used this system &#8211; unless their emails were leaked as a result of eavesdropping while they were being transmitted across the open Internet.</p>
<p>In the National Party case the journalist concerned has said several times that he was given the emails by someone with a right to have them. Crypto won&#8217;t fix that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim McKenzie</title>
		<link>http://it.gen.nz/2008/07/24/keeping-your-email-secure/comment-page-1/#comment-704</link>
		<dc:creator>Tim McKenzie</dc:creator>
		<pubDate>Mon, 28 Jul 2008 04:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://it.gen.nz/?p=130#comment-704</guid>
		<description>&quot;Nothing in email can be truly secure because its sent as plaintext across the Net&quot;.
What about public key cryptography? I would suggest that the National Party (and any other parties that are worried) should look at using that.</description>
		<content:encoded><![CDATA[<p>&#8220;Nothing in email can be truly secure because its sent as plaintext across the Net&#8221;.<br />
What about public key cryptography? I would suggest that the National Party (and any other parties that are worried) should look at using that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: colin</title>
		<link>http://it.gen.nz/2008/07/24/keeping-your-email-secure/comment-page-1/#comment-700</link>
		<dc:creator>colin</dc:creator>
		<pubDate>Thu, 24 Jul 2008 00:53:38 +0000</pubDate>
		<guid isPermaLink="false">http://it.gen.nz/?p=130#comment-700</guid>
		<description>Peter

You are right, I should have mentioned Pegasus even though client software wasn&#039;t my point today. David Harris - if you&#039;re reading this, sorry. Colin.</description>
		<content:encoded><![CDATA[<p>Peter</p>
<p>You are right, I should have mentioned Pegasus even though client software wasn&#8217;t my point today. David Harris &#8211; if you&#8217;re reading this, sorry. Colin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Lynch</title>
		<link>http://it.gen.nz/2008/07/24/keeping-your-email-secure/comment-page-1/#comment-699</link>
		<dc:creator>Peter Lynch</dc:creator>
		<pubDate>Thu, 24 Jul 2008 00:37:38 +0000</pubDate>
		<guid isPermaLink="false">http://it.gen.nz/?p=130#comment-699</guid>
		<description>Shame on you, Colin, for not mentioning Pegasus Mail, made right here in New Zealand.

p.s. the links to Google and Fastmail are not working.</description>
		<content:encoded><![CDATA[<p>Shame on you, Colin, for not mentioning Pegasus Mail, made right here in New Zealand.</p>
<p>p.s. the links to Google and Fastmail are not working.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

