<?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/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	>

<channel>
	<title>— Jürgen Kreileder</title>
	<atom:link href="/articles/tag/exploit/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>Software Engineer and Consultant</description>
	<lastBuildDate>Sat, 29 Oct 2016 01:51:01 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
<site xmlns="com-wordpress:feed-additions:1">5303222</site><image><title>Jürgen Kreileder</title><url>/jk-rss.jpg</url><link>/</link><width>144</width><height>114</height><description>Software Engineer and Consultant</description></image>	<item>
		<title>wordpress.org Cracked, Exploit in 2.1.1 Release</title>
		<link>/articles/wordpress-org-cracked-exploit-in-2-1-1-release/</link>
					<comments>/articles/wordpress-org-cracked-exploit-in-2-1-1-release/#comments</comments>
		
		<dc:creator><![CDATA[Jürgen Kreileder]]></dc:creator>
		<pubDate>Sat, 03 Mar 2007 03:08:33 +0000</pubDate>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[exploit]]></category>
		<category><![CDATA[rant]]></category>
		<guid isPermaLink="false">http://blog.blackdown.de/2007/03/03/wordpressorg-cracked-exploit-in-211-release/</guid>

					<description><![CDATA[As pointed out on the WordPress development blog, a cracker gained access to the wordpress.org servers and replaced the 2.1.1 download with a modified exploitable version. The exploitable download may have been on the site for three or four days! It may be a good idea for the WordPress developers to sign their releases with<br />[&#8594; <a href="/articles/wordpress-org-cracked-exploit-in-2-1-1-release/" class="more-link">Read the rest of this entry</a>]]]></description>
										<content:encoded><![CDATA[<p>As pointed out on the <a href="http://wordpress.org/development/2007/03/upgrade-212/">WordPress development blog</a>, a cracker gained access to the wordpress.org servers and replaced the 2.1.1 download with a modified exploitable version. The exploitable download may have been on the site for three or four days!</p>
<p>It may be a good idea for the <a href="http://wordpress.org/" rel="tag">WordPress</a> developers to sign their releases with a well known and trusted PGP key. This would allow people to verify that downloaded files are really what they should be!<br />
This is a well-established practice used by other projects, for example by the <a href="http://kernel.org/signature.html">Linux kernel</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>/articles/wordpress-org-cracked-exploit-in-2-1-1-release/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">49</post-id>	</item>
	</channel>
</rss>
