<?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>Tadlock Enterprises &#187; security</title>
	<atom:link href="http://www.tadlockenterprises.com/tag/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tadlockenterprises.com</link>
	<description>A specialized west coast firm focused on product and technology vision, planning and execution.</description>
	<lastBuildDate>Thu, 18 Mar 2010 07:45:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Ignore an Invalid SSL Cert in .NET</title>
		<link>http://www.tadlockenterprises.com/2010/03/ignore-an-invalid-ssl-cert-in-net/</link>
		<comments>http://www.tadlockenterprises.com/2010/03/ignore-an-invalid-ssl-cert-in-net/#comments</comments>
		<pubDate>Sat, 06 Mar 2010 01:08:13 +0000</pubDate>
		<dc:creator>Craig Tadlock</dc:creator>
				<category><![CDATA[development]]></category>
		<category><![CDATA[tips & tricks]]></category>
		<category><![CDATA[.net]]></category>
		<category><![CDATA[certificate]]></category>
		<category><![CDATA[IP]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[web service]]></category>

		<guid isPermaLink="false">http://www.tadlockenterprises.com/?p=456</guid>
		<description><![CDATA[One of our clients integrates with a financial services company which provides an API to access data. Obviously this needs to be secure. Their QA environment is secured via SSL but is exposed only by IP address. A .NET client will by default throw a security exception when you try to create a SSL connection [...]]]></description>
			<content:encoded><![CDATA[<p>One of our clients integrates with a financial services company which provides an API to access data. Obviously this needs to be secure. Their QA environment is secured via SSL but is exposed only by IP address. A .NET client will by default throw a security exception when you try to create a SSL connection by IP because the certificate has been issued to a name. This code will get you past that&#8230;</p>
<p><em>ServicePointManager.ServerCertificateValidationCallback += ((sender, certificate, chain, sslPolicyErrors) =&gt; true);</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.tadlockenterprises.com/2010/03/ignore-an-invalid-ssl-cert-in-net/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fix Loopback 401 Errors in Windows Server 2008</title>
		<link>http://www.tadlockenterprises.com/2010/02/fix-loopback-401-errors-in-windows-server-2008/</link>
		<comments>http://www.tadlockenterprises.com/2010/02/fix-loopback-401-errors-in-windows-server-2008/#comments</comments>
		<pubDate>Thu, 25 Feb 2010 08:13:16 +0000</pubDate>
		<dc:creator>Craig Tadlock</dc:creator>
				<category><![CDATA[it]]></category>
		<category><![CDATA[tips & tricks]]></category>
		<category><![CDATA[iis]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[regedit]]></category>
		<category><![CDATA[registry]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://www.tadlockenterprises.com/?p=446</guid>
		<description><![CDATA[If you use a loopback address (127.0.0.1) or hosts files on your Windows Server to reference a local IIS web application with Windows Authentication it will probably fail with a 401 error due to a new security constraint. This is often the case if you use a public url for your Sharepoint of TFS server. [...]]]></description>
			<content:encoded><![CDATA[<p>If you use a loopback address (127.0.0.1) or hosts files on your Windows Server to reference a local IIS web application with Windows Authentication it will probably fail with a 401 error due to a new security constraint. This is often the case if you use a public url for your Sharepoint of TFS server. To resolve this you need to add a registry key&#8230;</p>
<ol>
<li>Open <em>regedit</em></li>
<li>Open the key <em>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa</em></li>
<li>Create a new DWORD under <em>Lsa </em>named <em>DisableLoopbackCheck</em></li>
<li>Set its value to 1</li>
<li>Restart the server for good measure</li>
</ol>
<p><strong>Related Links</strong></p>
<p><a href="http://support.microsoft.com/kb/896861" target="_blank">http://support.microsoft.com/kb/896861</a></p>
<p><a href="http://ppalakollu.blogspot.com/2009/04/ie-8-ntlm-authentication-on-windows.html" target="_blank">http://ppalakollu.blogspot.com/2009/04/ie-8-ntlm-authentication-on-windows.html</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.tadlockenterprises.com/2010/02/fix-loopback-401-errors-in-windows-server-2008/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Hack a Wireless Network for $17</title>
		<link>http://www.tadlockenterprises.com/2009/12/hack-a-wireless-network-for-17/</link>
		<comments>http://www.tadlockenterprises.com/2009/12/hack-a-wireless-network-for-17/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 10:00:08 +0000</pubDate>
		<dc:creator>Craig Tadlock</dc:creator>
				<category><![CDATA[security]]></category>
		<category><![CDATA[cloud computing]]></category>
		<category><![CDATA[dictionary]]></category>
		<category><![CDATA[encryption]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[key]]></category>
		<category><![CDATA[psk]]></category>
		<category><![CDATA[wireless]]></category>
		<category><![CDATA[wpa]]></category>

		<guid isPermaLink="false">http://www.tadlockenterprises.com/?p=371</guid>
		<description><![CDATA[Cloud computing has started to change the way we think about building and hosting applications. The access to large computing resources on demand has allowed applications to rapidly handle their scaling needs. But it also has other uses&#8230; like breaking (oh, I mean testing) your (someone else&#8217;s) wireless network. WPA Cracker is a cloud solution [...]]]></description>
			<content:encoded><![CDATA[<p>Cloud computing has started to change the way we think about building and hosting applications. The access to large computing resources on demand has allowed applications to rapidly handle their scaling needs. But it also has other uses&#8230; like breaking (oh, I mean testing) your (someone else&#8217;s) wireless network. <a href="http://www.wpacracker.com" target="_blank">WPA Cracker</a> is a cloud solution to crack WPA-PSK wireless networks. It does this by leveraging a 400 CPU cluster and  a 135 million word dictionary. You just need to upload your network traffic capture to their server and after a bit of crunching it spits out they key. They claim it takes about 20 minutes to break, which will cost you all of $17. I think this is great. I&#8217;m pretty sure professional hacking groups had access to these types of resources in the past; so it&#8217;s really nothing new. Hopefully now that it has become a bit more public people will take the proper security steps to protect their networks, servers and data.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tadlockenterprises.com/2009/12/hack-a-wireless-network-for-17/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
