<?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>nFriedly Web Dev Tech Blog &#187; tls</title>
	<atom:link href="http://nfriedly.com/techblog/tag/tls/feed/" rel="self" type="application/rss+xml" />
	<link>http://nfriedly.com/techblog</link>
	<description>Expert Advice on Website Development, Javascript, Ajax, and Security</description>
	<lastBuildDate>Wed, 01 Feb 2012 22:35:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Why some users can&#8217;t see a https website</title>
		<link>http://nfriedly.com/techblog/2009/06/users-cant-see-https-website/</link>
		<comments>http://nfriedly.com/techblog/2009/06/users-cant-see-https-website/#comments</comments>
		<pubDate>Sun, 07 Jun 2009 05:02:13 +0000</pubDate>
		<dc:creator>nFriedly</dc:creator>
				<category><![CDATA[Web Development]]></category>
		<category><![CDATA[bugfix]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[tls]]></category>

		<guid isPermaLink="false">http://nfriedly.com/techblog/?p=1</guid>
		<description><![CDATA[Recently a client of mine had me pulling my hair out trying to figure out why some users couldn&#8217;t see the the secure https sections of their website. As it turned out,  the server had been upgraded to TLS only for PCI-compliance, and some users had TLS disabled. This article goes in to the how, [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-thumbnail wp-image-41" title="lock_small" src="http://nfriedly.com/techblog/wp-content/uploads/2009/06/lock_small-128x150.jpg" alt="lock_small" width="128" height="150" />Recently a client of mine had me pulling my hair out trying to figure out why some users couldn&#8217;t see the the secure https sections of their website.</p>
<p>As it turned out,  the server had been upgraded to TLS only for PCI-compliance, and some users had TLS disabled.</p>
<p>This article goes in to the how, they why, and the solution to fix https websites that aren&#8217;t showing up for some users.</p>
<p><span id="more-1"></span></p>
<h2>The Change</h2>
<p>Recently a client of mine made some changes to their secure server in order to comply with <acronym title="Payment Card Industry">PCI</acronym> regulations.</p>
<p>The rather cryptic error the PCI compliance scan gave was</p>
<pre><strong>Synopsis</strong> : The remote service supports the use of weak SSL ciphers.
<strong>Description</strong> : The remote host supports the use of SSL ciphers that offer either weak encryption or no encryption at all.
See also : http://www.openssl.org/docs/apps/ciphers .html
<strong>Solution</strong>: Reconfigure the affected application if possible to avoid use of weak ciphers.
<strong>Risk Factor</strong>: Medium  / CVSS
Base Score : 5.0 (CVSS2#AV:N/AC:L/Au:N/C:P/I:N/A:N)
Plugin output :
Here is the list of weak SSL ciphers supported by the remote server :
Low Strength Ciphers (&lt; 56-bit key) SSLv3 EXP-RC2-CBC-MD5 Kx=RSA(512) Au=RSA Enc=RC2(40) Mac=MD5 export EXP-RC4-MD5 Kx=RSA(512) Au=RSA Enc=RC4(40) Mac=MD5 export
The fields above are : {OpenSSL ciphername} Kx={key exchange} Au={authentication} Enc={symmetric encryption method} Mac={message authentication code} {export flag}</pre>
<p>They disabled <acronym title="Secure Socket Layer">SSL</acronym> 3.0 and lower in IIS and set it to  only accept <acronym title="Transport Layer Security">TLS</acronym> connections. (TLS is essentially SSL 4.0). This allowed them to pass the PCI compliance, but brought on new issues.</p>
<h2>The Problem</h2>
<p>Immediately after making this change, they began to get complaints from a few users who could no longer see the secure sections of their website.</p>
<p>Most of these users were on older versions of Internet Explorer, so they were first asked to upgrade to the<a rel="nofollow" href="http://www.microsoft.com/windows/internet-explorer/"> latest version</a>. This didn&#8217;t fix the issue for most of them.</p>
<h2>The Fix</h2>
<p>After some digging around, I learned the IE has settings for disabling SSL &amp; TLS.</p>
<ol>
<li>In Internet Explorer on the <strong>Tools</strong> menu, choose <strong>Internet Options</strong>.</li>
<li>Go to the <strong>Advanced</strong> tab.</li>
<li>Scroll all the way to the bottom and check &#8216;<strong>Use <span class="il">TLS</span> 1.0</strong>&#8216;</li>
<li> Click Ok. You may need to restart your browser.</li>
</ol>
<p>I have <em>no idea</em> why that would ever get unchecked, but apparently it happens.  It&#8217;s also worth noting that upgrading to a newer version keeps the old settings intact.</p>
<h2>Need help with a secure website?</h2>
<p>I have significant experience in <a href="http://nfriedly.com/webdev">e-commerce</a> and other security heavy areas.  If you need <a href="http://nfriedly.com/webdev">secure web development</a>, I can probably help you out.  I understand https from the high level implementation right down to the <a href="http://nfriedly.com/stuff/Nathan_Friedly_SSL_TLS.doc">bits and bytes</a> (.doc file).</p>
]]></content:encoded>
			<wfw:commentRss>http://nfriedly.com/techblog/2009/06/users-cant-see-https-website/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

