<?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>blog.dev001.net &#187; security</title>
	<atom:link href="http://blog.dev001.net/tag/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dev001.net</link>
	<description>Just another Web Developer's weblog</description>
	<lastBuildDate>Thu, 29 Jul 2010 12:18:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Rails: Digitally sign outgoing emails (S/MIME)</title>
		<link>http://blog.dev001.net/2009/04/rails-digitally-sign-outgoing-emails-smime/</link>
		<comments>http://blog.dev001.net/2009/04/rails-digitally-sign-outgoing-emails-smime/#comments</comments>
		<pubDate>Wed, 22 Apr 2009 11:37:55 +0000</pubDate>
		<dc:creator>rfc2822</dc:creator>
				<category><![CDATA[Web Development]]></category>
		<category><![CDATA[Rails]]></category>
		<category><![CDATA[S/MIME]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://blog.dev001.net/?p=189</guid>
		<description><![CDATA[In this article, I will introduce one method to digitally sign outgoing emails with S/MIME using Ruby on Rails. require &#8216;openssl&#8217; vs. Kernel.system openssl At first, I tried to sign mails using the Ruby OpenSSL library which is basically a lightweight wrapper for libopenssl. However, I was not successful; I found out how to create [...]]]></description>
		<wfw:commentRss>http://blog.dev001.net/2009/04/rails-digitally-sign-outgoing-emails-smime/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Typo3: still 30 % vulnerable to latest critical security hole</title>
		<link>http://blog.dev001.net/2009/02/typo3-still-30-vulnerable-to-latest-critical-security-hole/</link>
		<comments>http://blog.dev001.net/2009/02/typo3-still-30-vulnerable-to-latest-critical-security-hole/#comments</comments>
		<pubDate>Sun, 15 Feb 2009 18:22:04 +0000</pubDate>
		<dc:creator>rfc2822</dc:creator>
				<category><![CDATA[Web Development]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[typo3]]></category>

		<guid isPermaLink="false">http://blog.dev001.net/?p=137</guid>
		<description><![CDATA[A quick scan of sites made with Typo3 told me that 99 of 330 pages are still vulnerable to the last Typo3 security bug that allows to read all .php files, including localconf.php (where the database password and other things ard stored) at the moment. That means that about 30 % of all Typo3 pages [...]]]></description>
		<wfw:commentRss>http://blog.dev001.net/2009/02/typo3-still-30-vulnerable-to-latest-critical-security-hole/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
