<?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>Secure Tomorrow &#187; website security</title>
	<atom:link href="http://www.securetomorrow.org/tag/website-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.securetomorrow.org</link>
	<description>Kevin Blanchard's Information Security Blog</description>
	<lastBuildDate>Thu, 30 Jul 2009 20:51:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>PHP forum systems inherit phpBB vulnerability</title>
		<link>http://www.securetomorrow.org/2007/02/php-forum-systems-inherit-phpbb-vulnerability/</link>
		<comments>http://www.securetomorrow.org/2007/02/php-forum-systems-inherit-phpbb-vulnerability/#comments</comments>
		<pubDate>Mon, 05 Feb 2007 04:14:00 +0000</pubDate>
		<dc:creator>Kevin Blanchard</dc:creator>
				<category><![CDATA[post]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[phpBB]]></category>
		<category><![CDATA[website security]]></category>

		<guid isPermaLink="false">http://www.securetomorrow.org/wp/?p=19</guid>
		<description><![CDATA[For any of you running a phpBB based setup, if there was one idea I could get across to you, underlined, bolded and with 17 exclamation marks is make sure you set register_globals to off. Now that I have gotten that out of the way, Heise Security has a short article up discussing the matter [...]]]></description>
			<content:encoded><![CDATA[<p>For any of you running a phpBB based setup, if there was one idea I could get across to you, underlined, bolded and with 17 exclamation marks is <span style="font-weight:bold;">make sure you set register_globals to off</span>.</p>
<p>Now that I have gotten that out of the way, <a href="http://www.heise-security.co.uk">Heise Security</a> has a short article up discussing the matter in a bit more detail.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.securetomorrow.org/2007/02/php-forum-systems-inherit-phpbb-vulnerability/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>Nmap 4.00 is here</title>
		<link>http://www.securetomorrow.org/2006/02/nmap-400-is-here/</link>
		<comments>http://www.securetomorrow.org/2006/02/nmap-400-is-here/#comments</comments>
		<pubDate>Sat, 04 Feb 2006 01:19:00 +0000</pubDate>
		<dc:creator>Kevin Blanchard</dc:creator>
				<category><![CDATA[post]]></category>
		<category><![CDATA[network security]]></category>
		<category><![CDATA[Nmap]]></category>
		<category><![CDATA[system security]]></category>
		<category><![CDATA[website security]]></category>

		<guid isPermaLink="false">http://www.securetomorrow.org/wp/?p=9</guid>
		<description><![CDATA[Not much more to say about it. If you use it, you are probably as excited as I am. If you don&#8217;t&#8230; then go download it. It&#8217;s a valuable tool that should be in any security engineers arsenal. Related links: Documentation: http://www.insecure.org/nmap/docs.html Download: http://www.insecure.org/nmap/download.html Release Announcement: http://www.insecure.org/stf/Nmap-4.00-Release.html]]></description>
			<content:encoded><![CDATA[<p>Not much more to say about it. If you use it, you are probably as excited as I am. If you don&#8217;t&#8230; then go download it. It&#8217;s a valuable tool that should be in any security engineers arsenal.</p>
<p><span style="font-weight:bold;">Related links:</span><br />
Documentation: <a href="http://www.insecure.org/nmap/docs.html">http://www.insecure.org/nmap/docs.html</a><br />
Download: <a href="http://www.insecure.org/nmap/download.html">http://www.insecure.org/nmap/download.html</a><br />
Release Announcement: <a href="http://www.insecure.org/stf/Nmap-4.00-Release.html">http://www.insecure.org/stf/Nmap-4.00-Release.html</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.securetomorrow.org/2006/02/nmap-400-is-here/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nmap + Perl &gt; case of the Mondays</title>
		<link>http://www.securetomorrow.org/2005/12/nmap-perl-case-of-the-mondays/</link>
		<comments>http://www.securetomorrow.org/2005/12/nmap-perl-case-of-the-mondays/#comments</comments>
		<pubDate>Sat, 10 Dec 2005 08:56:00 +0000</pubDate>
		<dc:creator>Kevin Blanchard</dc:creator>
				<category><![CDATA[post]]></category>
		<category><![CDATA[network security]]></category>
		<category><![CDATA[Nmap]]></category>
		<category><![CDATA[system security]]></category>
		<category><![CDATA[website security]]></category>

		<guid isPermaLink="false">http://www.securetomorrow.org/wp/?p=8</guid>
		<description><![CDATA[SANS diary had a neat little trick posted a couple weeks back. For those of you who use Nmap quite a bit or as part of their day to day at work, here&#8217;s a tip that might help make your work week a bit more bearable. You are aware of the XML output from Nmap [...]]]></description>
			<content:encoded><![CDATA[<p>SANS diary had a neat little trick posted a couple weeks back. For those of you who use Nmap quite a bit or as part of their day to day at work, here&#8217;s a tip that might help make your work week a bit more bearable. You are aware of the XML output from Nmap but what the heck do you do with it? Perl has a module that just might help you out called NMAP::Parser. This might make your job analyzing or reacting to your findings a bit easier. If you still aren&#8217;t 100% clear on how you might use it, <a href="http://handlers.sans.org/khaugsness/">here is more information along with an example</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.securetomorrow.org/2005/12/nmap-perl-case-of-the-mondays/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

