<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	
	>
<channel>
	<title>
	Comments on: Another WordPress Security Update	</title>
	<atom:link href="/articles/another-wordpress-security-update/feed/" rel="self" type="application/rss+xml" />
	<link>/articles/another-wordpress-security-update/</link>
	<description>Software Engineer and Consultant</description>
	<lastBuildDate>Sat, 29 Oct 2016 01:51:02 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: &#187; WordPress 1.5.2 Released TurboBlogger.com		</title>
		<link>/articles/another-wordpress-security-update/comment-page-1/#comment-74</link>

		<dc:creator><![CDATA[&#187; WordPress 1.5.2 Released TurboBlogger.com]]></dc:creator>
		<pubDate>Mon, 15 Aug 2005 20:35:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/08/14/another-wordpress-security-update/#comment-74</guid>

					<description><![CDATA[[...] While Matt &#038; Co are keeping mum on the exact vulnerabilities that are being fixed, they claim to be doing so because there is already at least one exploit out in the wild and they believe releasing that info will simply make it easier for more exploits to be designed. I&#8217;m going to have to agree with Duncan Riley and some others that this type of security by obscurity is not appropriate. [...]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] While Matt &#38; Co are keeping mum on the exact vulnerabilities that are being fixed, they claim to be doing so because there is already at least one exploit out in the wild and they believe releasing that info will simply make it easier for more exploits to be designed. I&#8217;m going to have to agree with Duncan Riley and some others that this type of security by obscurity is not appropriate. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Christoph Hoerl		</title>
		<link>/articles/another-wordpress-security-update/comment-page-1/#comment-73</link>

		<dc:creator><![CDATA[Christoph Hoerl]]></dc:creator>
		<pubDate>Mon, 15 Aug 2005 16:09:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/08/14/another-wordpress-security-update/#comment-73</guid>

					<description><![CDATA[Have you seen &lt;a href=&quot;http://wordpress.org/support/topic/41894&quot; rel=&quot;nofollow&quot;&gt;this page&lt;/a&gt; in Wordpress Support? There a few more informations about the changes in 1.5.2.]]></description>
			<content:encoded><![CDATA[<p>Have you seen <a href="http://wordpress.org/support/topic/41894" rel="nofollow">this page</a> in WordPress Support? There a few more informations about the changes in 1.5.2.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: christoph-hoerl.de		</title>
		<link>/articles/another-wordpress-security-update/comment-page-1/#comment-72</link>

		<dc:creator><![CDATA[christoph-hoerl.de]]></dc:creator>
		<pubDate>Mon, 15 Aug 2005 16:07:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/08/14/another-wordpress-security-update/#comment-72</guid>

					<description><![CDATA[&lt;strong&gt;Wordpress 1.5.2&lt;/strong&gt;

	
Gestern wurde die Version 1.5.2 von Wordpress veröffentlicht. Wie im Weblog deutlich wird, wurden keine sichtbaren Updates vorgenommen. Hauptsächlich wurden Sicherheitslücken geschlossen. Eine detaillierte Liste der Änderungen gibt es im Support....]]></description>
			<content:encoded><![CDATA[<p><strong>WordPress 1.5.2</strong></p>
<p>Gestern wurde die Version 1.5.2 von WordPress veröffentlicht. Wie im Weblog deutlich wird, wurden keine sichtbaren Updates vorgenommen. Hauptsächlich wurden Sicherheitslücken geschlossen. Eine detaillierte Liste der Änderungen gibt es im Support&#8230;.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: lobstertechnology.com		</title>
		<link>/articles/another-wordpress-security-update/comment-page-1/#comment-71</link>

		<dc:creator><![CDATA[lobstertechnology.com]]></dc:creator>
		<pubDate>Mon, 15 Aug 2005 12:10:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/08/14/another-wordpress-security-update/#comment-71</guid>

					<description><![CDATA[&lt;strong&gt;Changes in Wordpress 1.5.2&lt;/strong&gt;

	my 2 cents&#8230;

...]]></description>
			<content:encoded><![CDATA[<p><strong>Changes in WordPress 1.5.2</strong></p>
<p>	my 2 cents&#8230;</p>
<p>&#8230;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: cyDome		</title>
		<link>/articles/another-wordpress-security-update/comment-page-1/#comment-70</link>

		<dc:creator><![CDATA[cyDome]]></dc:creator>
		<pubDate>Mon, 15 Aug 2005 09:41:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/08/14/another-wordpress-security-update/#comment-70</guid>

					<description><![CDATA[&lt;strong&gt;WordPress-Team verheimlicht Details über Sicherheitslücken&lt;/strong&gt;

	Wordpress 1.5.2 ist jetzt verfügbar. Das Update enthält einige sicherheitsrelevante Bugfixes. Jürgen Kreileder beschwert sich, dass man keine Details über die Art der Sicherheitslücken erfährt:
	
 I hate that kind of silly security by obscurity....]]></description>
			<content:encoded><![CDATA[<p><strong>WordPress-Team verheimlicht Details über Sicherheitslücken</strong></p>
<p>	Wordpress 1.5.2 ist jetzt verfügbar. Das Update enthält einige sicherheitsrelevante Bugfixes. Jürgen Kreileder beschwert sich, dass man keine Details über die Art der Sicherheitslücken erfährt:</p>
<p> I hate that kind of silly security by obscurity&#8230;.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: &#187; WordPress 1.5.2 released The Blog Herald: more blog news more often		</title>
		<link>/articles/another-wordpress-security-update/comment-page-1/#comment-69</link>

		<dc:creator><![CDATA[&#187; WordPress 1.5.2 released The Blog Herald: more blog news more often]]></dc:creator>
		<pubDate>Mon, 15 Aug 2005 01:35:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.blackdown.de/2005/08/14/another-wordpress-security-update/#comment-69</guid>

					<description><![CDATA[[...] I&#8217;ve got to agree with the comments over at No Wow though:  &#8220;The changelog mentions that several vulnerabilities have been fixed but — once again — the developers don’t provide any details! One has to look at the diffs to see what has been fixed&#8230; I hate that kind of silly security by obscurity. Vague vulnerability are almost useless for administrators, just saying “we’ve fixed some security problems” is even worse!&#8221; [...]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] I&#8217;ve got to agree with the comments over at No Wow though:  &#8220;The changelog mentions that several vulnerabilities have been fixed but — once again — the developers don’t provide any details! One has to look at the diffs to see what has been fixed&#8230; I hate that kind of silly security by obscurity. Vague vulnerability are almost useless for administrators, just saying “we’ve fixed some security problems” is even worse!&#8221; [&#8230;]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
