<?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>sporticia &#187; security</title>
	<atom:link href="http://www.sporticia.com/blog/category/security/feed" rel="self" type="application/rss+xml" />
	<link>http://www.sporticia.com/blog</link>
	<description>stuff I know, stuff I discover, stuff I see.......just stuff really</description>
	<lastBuildDate>Tue, 07 Feb 2012 14:25:58 +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>Apache Header Byte Range DoS Exploit&#8230;&#8230;.</title>
		<link>http://www.sporticia.com/blog/security/apache-header-byte-range-dos-exploit</link>
		<comments>http://www.sporticia.com/blog/security/apache-header-byte-range-dos-exploit#comments</comments>
		<pubDate>Fri, 02 Sep 2011 23:54:24 +0000</pubDate>
		<dc:creator>scottb</dc:creator>
				<category><![CDATA[apache]]></category>
		<category><![CDATA[internet]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[unix]]></category>
		<category><![CDATA[exploit]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://www.sporticia.com/blog/?p=1168</guid>
		<description><![CDATA[Grrrrr, looks like there&#8217;s an unpatched exploit in *all* versions of Apache web server. Is to do with using header byte ranges which allow http responses to be broken into smaller chunks before sending. You can read about them here and here. There are multiple workarounds for mitigating the issue that can be read here [...]]]></description>
		<wfw:commentRss>http://www.sporticia.com/blog/security/apache-header-byte-range-dos-exploit/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Over Zealous Registry Editing&#8230;&#8230;.Damn !</title>
		<link>http://www.sporticia.com/blog/microsoft/over-zealous-registry-editing-damn</link>
		<comments>http://www.sporticia.com/blog/microsoft/over-zealous-registry-editing-damn#comments</comments>
		<pubDate>Wed, 21 Apr 2010 09:25:19 +0000</pubDate>
		<dc:creator>scottb</dc:creator>
				<category><![CDATA[microsoft]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[xp]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[registry]]></category>
		<category><![CDATA[xp antivirus 2010]]></category>

		<guid isPermaLink="false">http://www.sporticia.com/blog/?p=607</guid>
		<description><![CDATA[The company where I work produces a web site. In order to make sure it looks ok on as many browsers as possible, we have to keep a few machines around with older OS and broswers versions installed. Last week, the machine used to test IE6 (now dead and unsupported by Microsoft, but unfortunately while [...]]]></description>
		<wfw:commentRss>http://www.sporticia.com/blog/microsoft/over-zealous-registry-editing-damn/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Refreshingly Secure&#8230;&#8230;.Part 3</title>
		<link>http://www.sporticia.com/blog/security/refreshingly-secure-pt-3</link>
		<comments>http://www.sporticia.com/blog/security/refreshingly-secure-pt-3#comments</comments>
		<pubDate>Mon, 04 Jan 2010 11:36:05 +0000</pubDate>
		<dc:creator>scottb</dc:creator>
				<category><![CDATA[apache]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[unix]]></category>

		<guid isPermaLink="false">http://www.sporticia.com/blog/?p=347</guid>
		<description><![CDATA[For the final part of reminding myself how to secure a linux website, I need to include the bit on how to force unsecure traffic to be secure. This is done using rewrite rules to rewrite the url path from http:// to https:// you can make the whole site redirect to secure, or just certain [...]]]></description>
		<wfw:commentRss>http://www.sporticia.com/blog/security/refreshingly-secure-pt-3/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Refreshingly Secure&#8230;&#8230;.Part 2</title>
		<link>http://www.sporticia.com/blog/security/refreshingly-secure-pt-2</link>
		<comments>http://www.sporticia.com/blog/security/refreshingly-secure-pt-2#comments</comments>
		<pubDate>Tue, 22 Dec 2009 11:16:39 +0000</pubDate>
		<dc:creator>scottb</dc:creator>
				<category><![CDATA[apache]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[unix]]></category>

		<guid isPermaLink="false">http://www.sporticia.com/blog/?p=344</guid>
		<description><![CDATA[So we now have our private key .key and our public key .crt (or something to that effect). Now we need include the files in the apache config. place the .key and .crt files where you can find them (I use /etc/apache/ssl-certs/). now you need to edit your apache config file. I&#8217;ve included a dummy [...]]]></description>
		<wfw:commentRss>http://www.sporticia.com/blog/security/refreshingly-secure-pt-2/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Refreshingly Secure&#8230;&#8230;.Part 1</title>
		<link>http://www.sporticia.com/blog/security/refreshingly-secure-pt-1</link>
		<comments>http://www.sporticia.com/blog/security/refreshingly-secure-pt-1#comments</comments>
		<pubDate>Fri, 18 Dec 2009 15:45:51 +0000</pubDate>
		<dc:creator>scottb</dc:creator>
				<category><![CDATA[apache]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[unix]]></category>

		<guid isPermaLink="false">http://www.sporticia.com/blog/?p=315</guid>
		<description><![CDATA[Grrrrrr, some of our SSL certificates had expired on a linux server today. And, like very time I have to renew an SSL on a linux machine, there was a bit of trial and error as I tried to remember how I did it the last time. So here&#8217;s a refresher for me and notes [...]]]></description>
		<wfw:commentRss>http://www.sporticia.com/blog/security/refreshingly-secure-pt-1/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

