<?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>Elephantsquared. &#187; tls</title>
	<atom:link href="http://elephantsquared.com/tag/tls/feed/" rel="self" type="application/rss+xml" />
	<link>http://elephantsquared.com</link>
	<description>hypertext &#38; software</description>
	<lastBuildDate>Sat, 19 May 2012 10:59:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Gmail, Security and the vulnerability in SSL/TLS protocol</title>
		<link>http://elephantsquared.com/2010/01/gmail-security-and-the-vulnerability-in-ssl-tls-protocol/</link>
		<comments>http://elephantsquared.com/2010/01/gmail-security-and-the-vulnerability-in-ssl-tls-protocol/#comments</comments>
		<pubDate>Wed, 13 Jan 2010 19:18:25 +0000</pubDate>
		<dc:creator>George T</dc:creator>
				<category><![CDATA[google]]></category>
		<category><![CDATA[add-on]]></category>
		<category><![CDATA[cryptography]]></category>
		<category><![CDATA[end-to-end]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[forcehttps]]></category>
		<category><![CDATA[gmail]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[protocol]]></category>
		<category><![CDATA[quantum]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[tls]]></category>

		<guid isPermaLink="false">http://elephantsquared.com/?p=1213</guid>
		<description><![CDATA[Back in 2008, Google released a nice feature inside Gmail&#8217;s settings where you could opt to enable https throughout your session. That made you feel a little bit safer when browsing your emails using a public WiFi at your local coffee shop. However, the usage of SSL/TLS protocol has one main drawback which is imposing [...]]]></description>
			<content:encoded><![CDATA[<p>Back in 2008, Google <a href="http://gmailblog.blogspot.com/2008/07/making-security-easier.html" target="_blank">released</a> a nice feature inside Gmail&#8217;s settings where you could opt to enable <strong>https</strong> throughout your session. That made you feel a little bit safer when browsing your emails using a public WiFi at your local coffee shop. However, the usage of SSL/TLS protocol has one main drawback which is imposing some extra overhead. Thus causing some extra latency. This latency could be noticeable a few years ago when the average broadband speed did not exceed 1 Mbps in contrary to nowadays. So after <a href="http://googleonlinesecurity.blogspot.com/2009/06/https-security-for-web-applications.html" target="_blank">researching the security/latency tradeoff</a>, Google <a href="http://gmailblog.blogspot.com/2010/01/default-https-access-for-gmail.html" target="_blank">decided</a> to roll out default https for all Gmail users for the sake of security (you can still turn it off at any time but https will still be &#8220;on&#8221; when you login).</p>
<p>About two months ago, I came across with a couple of interesting articles at the <a href="http://h-online.com" target="_blank">h-online.com</a> regarding a <a href="http://www.h-online.com/open/news/item/Vulnerability-in-SSL-TLS-protocol-851478.html" target="_blank">vulnerability in SSL/TLS protocol</a> which could lead to <a href="http://www.h-online.com/open/news/item/Password-theft-via-vulnerability-in-SSL-TLS-protocol-860435.html" target="_blank">password theft</a>. It is surprising that something we used to trust for years now has been compromised. At first I thought &#8220;what the heck..?!&#8221;. Indeed, what&#8217;s the point of choosing to use https or not at all. Well, the truth is that if you are investing in 100% security you are wasting your money. Unfortunately there is no such thing as 100% secure (at least for the time being). The good news is that there seems to be a solution to the TLS vulnerability. <a href="http://www.h-online.com/security/news/item/Solution-for-SSL-TLS-design-weakness-in-sight-902887.html" target="_blank">According</a> to <strong>H-online</strong>:</p>
<blockquote><p>The Internet Engineering Task Force (IETF) has ammended the RFC 5246 specification (Transport Layer Security [TLS] Protocol Version 1.2) and introduced a new <em>renegotiation_info</em> TLS extension which will store a connection&#8217;s cryptographic information.</p></blockquote>
<p>If you ask me, there is nothing even close to 100% secure. The harsh truth is even when quantum cryptography will be applicable somehow, end-to-end security will still suffer from various kinds of attacks. Still having second thoughts every time you try to login somewhere..? In that case you should check out <a href="https://crypto.stanford.edu/forcehttps/" target="_blank">ForceHTTPS</a> (a Firefox add-on) which forces https &#8220;every&#8221; time you hit the enter button.</p>
<blockquote><p>ForceHTTPS allows sophisticated users to transparently retrofit security onto some insecure sites that support HTTPS.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://elephantsquared.com/2010/01/gmail-security-and-the-vulnerability-in-ssl-tls-protocol/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

