<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Jim's Blog &#187; verisign is evil</title>
	<atom:link href="http://blog.jim.com/tag/verisign-is-evil/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.jim.com</link>
	<description>Liberty in an unfree world</description>
	<lastBuildDate>Fri, 03 Sep 2010 02:49:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>One mode, and it is secure</title>
		<link>http://blog.jim.com/crypto/one-mode-and-it-is-secure.html</link>
		<comments>http://blog.jim.com/crypto/one-mode-and-it-is-secure.html#comments</comments>
		<pubDate>Tue, 24 Jun 2008 01:03:16 +0000</pubDate>
		<dc:creator>jim</dc:creator>
				<category><![CDATA[crypto]]></category>
		<category><![CDATA[one mode]]></category>
		<category><![CDATA[pki]]></category>
		<category><![CDATA[verisign is evil]]></category>

		<guid isPermaLink="false">http://blog.jim.com/?p=205</guid>
		<description><![CDATA[Ian Grigg correctly argues that any internet protocol that has an insecure mode can never be made secure, thus if security is introduced as after thought, will never be secure. Https is exactly such a bolted on afterthought, and to use it one must pay money, and suffer substantial inconvenience. Further, it is a woefully [...]]]></description>
			<content:encoded><![CDATA[<p>Ian Grigg correctly<a href="https://financialcryptography.com/mt/archives/001067.html"> argues that any internet protocol that has an insecure mode can never be made secure</a>, thus if security is introduced as after thought, will never be secure.</p>
<p>Https is exactly such a bolted on afterthought, and to use it one must pay money, and suffer substantial inconvenience. Further, it is a woefully inefficient protocol, so people always try to minimize their use of it to only what is truly necessary, which they are unlikely to ever do correctly. Further, those to whom one must pay money are themselves a point of failure, not a source of security.</p>
<p>Iang attempts, and fails, to make his website conform to the <strong style="color: black; background-color: #ffff66;">one mode</strong> principle.  For a blog to implement “the <strong style="color: black; background-color: #ffff66;">one mode</strong> and it is secure” paradigm it must be accessed by https, and accessing it by http should generate an 301 redirect to the https site. The trouble is, that when one reaches the https site, the site has to have a certificate whose root is accepted by the big browsers, typically a Verisign certificate. Such certificates are a pain to get, and a pain to install. And so, no one ever does. Iang has not got a big name certificate in the appropriate name for his web site, so accessing his site correctly generates no end of alarming error dialogs.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.jim.com/crypto/one-mode-and-it-is-secure.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
