<?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>ssl | RobWillis.info</title>
	<atom:link href="/tag/ssl/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>#yolosec</description>
	<lastBuildDate>Mon, 27 Jun 2022 04:55:35 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
	<item>
		<title>IIS 8 with ECC certificates &#8211; increasing your SSL Security on Windows Server 2012</title>
		<link>/2016/02/iis-8-with-ecc-certificates-increasing-your-ssl-security-on-windows-server-2012/</link>
		
		<dc:creator><![CDATA[robwillisinfo]]></dc:creator>
		<pubDate>Fri, 12 Feb 2016 10:20:26 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Computers]]></category>
		<category><![CDATA[Servers]]></category>
		<category><![CDATA[2012]]></category>
		<category><![CDATA[2012 R2]]></category>
		<category><![CDATA[AES]]></category>
		<category><![CDATA[CSR]]></category>
		<category><![CDATA[ECC]]></category>
		<category><![CDATA[ECDHE]]></category>
		<category><![CDATA[ECDSA]]></category>
		<category><![CDATA[Elliptic Curve Cryptography]]></category>
		<category><![CDATA[GCM]]></category>
		<category><![CDATA[IIS]]></category>
		<category><![CDATA[Obsolete Cryotography]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[tls]]></category>
		<category><![CDATA[Windows Server]]></category>
		<guid isPermaLink="false">/?p=2624</guid>

					<description><![CDATA[<p>What is an ECC Certificate and why would you need one? The main difference with an Elliptic Curve Cryptography (ECC) certificate is with how the certificate is signed, in this case the Elliptic Curve Digital Signature Algorithm (ECDSA) is used vs the standard RSA we are used to seeing. Once you have a certificate signed [&#8230;]</p>
The post <a href="/2016/02/iis-8-with-ecc-certificates-increasing-your-ssl-security-on-windows-server-2012/">IIS 8 with ECC certificates – increasing your SSL Security on Windows Server 2012</a> first appeared on <a href="/">RobWillis.info</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>Hardening SSL &#038; TLS connections on Windows Server 2008 R2 &#038; 2012 R2</title>
		<link>/2015/10/hardening-ssl-tls-connections-on-windows-server-2008-r2-2012-r2/</link>
		
		<dc:creator><![CDATA[robwillisinfo]]></dc:creator>
		<pubDate>Wed, 21 Oct 2015 10:02:34 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Computers]]></category>
		<category><![CDATA[Servers]]></category>
		<category><![CDATA[Cipher]]></category>
		<category><![CDATA[DHE]]></category>
		<category><![CDATA[Disable]]></category>
		<category><![CDATA[hardening]]></category>
		<category><![CDATA[https]]></category>
		<category><![CDATA[IIS]]></category>
		<category><![CDATA[MS SQL]]></category>
		<category><![CDATA[PCI compliance]]></category>
		<category><![CDATA[qualys]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[SSL V3]]></category>
		<category><![CDATA[Suite]]></category>
		<category><![CDATA[tls]]></category>
		<category><![CDATA[TLS 1]]></category>
		<guid isPermaLink="false">/?p=2455</guid>

					<description><![CDATA[<p>Hardening your SSL/TLS connections is a pretty common thing to do on any Windows Server running IIS and web applications that utilize HTTPS, especially if they require some sort of compliance. It is generally a good idea to do this on all of your servers though, to ensure your secure connections really are secure. On [&#8230;]</p>
The post <a href="/2015/10/hardening-ssl-tls-connections-on-windows-server-2008-r2-2012-r2/">Hardening SSL & TLS connections on Windows Server 2008 R2 & 2012 R2</a> first appeared on <a href="/">RobWillis.info</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>Disabling TLS 1.0 with MS SQL 2012/2014 &#8211; Services won&#8217;t start &#038; SSMS fails to connect</title>
		<link>/2015/08/disabling-tls-1-0-with-ms-sql-2014-services-wont-start/</link>
		
		<dc:creator><![CDATA[robwillisinfo]]></dc:creator>
		<pubDate>Sun, 16 Aug 2015 08:22:32 +0000</pubDate>
				<category><![CDATA[Servers]]></category>
		<category><![CDATA[.Net]]></category>
		<category><![CDATA[MS SQL]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[Server Agent]]></category>
		<category><![CDATA[Service won't start]]></category>
		<category><![CDATA[services fail]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[ssms]]></category>
		<category><![CDATA[tls]]></category>
		<category><![CDATA[Windows]]></category>
		<guid isPermaLink="false">/?p=2417</guid>

					<description><![CDATA[<p>Update &#8211; 2.1.2016 &#8211; I would really only use this as a last resort and I highly recommend testing this solution prior to putting it into production. At this time it does not appear that all of SQL&#8217;s features fully support disabling TLS 1.0 and you may run into issues with things like Reporting Services(SSRS). [&#8230;]</p>
The post <a href="/2015/08/disabling-tls-1-0-with-ms-sql-2014-services-wont-start/">Disabling TLS 1.0 with MS SQL 2012/2014 – Services won’t start & SSMS fails to connect</a> first appeared on <a href="/">RobWillis.info</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>Fix the obsolete cryptography warning in Chrome on IIS 7 &#038; 8</title>
		<link>/2015/05/fix-obsolete-cryptography-warning-in-chrome-on-iis-8/</link>
		
		<dc:creator><![CDATA[robwillisinfo]]></dc:creator>
		<pubDate>Sat, 02 May 2015 09:01:40 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Computers]]></category>
		<category><![CDATA[Servers]]></category>
		<category><![CDATA[browser]]></category>
		<category><![CDATA[chrome]]></category>
		<category><![CDATA[cryptography]]></category>
		<category><![CDATA[fix]]></category>
		<category><![CDATA[IIS]]></category>
		<category><![CDATA[iis 7]]></category>
		<category><![CDATA[iis 8]]></category>
		<category><![CDATA[obsolete cryptography]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[tls]]></category>
		<category><![CDATA[warning]]></category>
		<category><![CDATA[web site]]></category>
		<category><![CDATA[Windows]]></category>
		<guid isPermaLink="false">/?p=2375</guid>

					<description><![CDATA[<p>Update &#8211; 2.2.2016 &#8211; The ciphers originally listed in this post no longer work to fix the obsolete cryptography warning as Google has upped the requirement from DHE with AES_128_GCM to ECDHE with AES_128_GCM or CHACHA20_POLY1305. The only ciphers we have on Windows that are close to this requirement are all ECDHE-ECDSA which will require [&#8230;]</p>
The post <a href="/2015/05/fix-obsolete-cryptography-warning-in-chrome-on-iis-8/">Fix the obsolete cryptography warning in Chrome on IIS 7 & 8</a> first appeared on <a href="/">RobWillis.info</a>.]]></description>
		
		
		
			</item>
		<item>
		<title>IIS 7/7.5 Hardening SSL TLS &#8211; Windows Server 2008 R2</title>
		<link>/2013/09/iis-77-5-hardening-ssl-tls-windows-server-2008-r2/</link>
		
		<dc:creator><![CDATA[robwillisinfo]]></dc:creator>
		<pubDate>Sat, 21 Sep 2013 00:40:52 +0000</pubDate>
				<category><![CDATA[Servers]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[beast]]></category>
		<category><![CDATA[exploit]]></category>
		<category><![CDATA[hardening]]></category>
		<category><![CDATA[IIS]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[tls]]></category>
		<category><![CDATA[vulnerability]]></category>
		<category><![CDATA[Windows]]></category>
		<guid isPermaLink="false">/?p=2098</guid>

					<description><![CDATA[<p>&#160;&#160;&#160;&#160;&#160;One of the first steps you should do when deploying a new public facing web server is hardening your server&#8217;s SSL/TLS connections. Disabling vulnerable protocols, ciphers, hashes and key exchange algorithms can help mitigate the now more common exploits like the BEAST attack. By default many weaker technologies are enabled, leaving IIS traffic vulnerable and [&#8230;]</p>
The post <a href="/2013/09/iis-77-5-hardening-ssl-tls-windows-server-2008-r2/">IIS 7/7.5 Hardening SSL TLS – Windows Server 2008 R2</a> first appeared on <a href="/">RobWillis.info</a>.]]></description>
		
		
		
			</item>
	</channel>
</rss>
