<?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>MS SQL | RobWillis.info</title>
	<atom:link href="/tag/ms-sql/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>#yolosec</description>
	<lastBuildDate>Thu, 13 Apr 2017 09:03:38 +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>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>
	</channel>
</rss>
