<?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/"
		>
<channel>
	<title>Comments on: Wordpress cookie authentication vulnerability</title>
	<atom:link href="http://www.lightbluetouchpaper.org/2007/11/20/wordpress-cookie-authentication-vulnerability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lightbluetouchpaper.org/2007/11/20/wordpress-cookie-authentication-vulnerability/</link>
	<description>Security Research, Computer Laboratory, University of Cambridge</description>
	<lastBuildDate>Fri, 10 Feb 2012 17:31:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Steven J. Murdoch</title>
		<link>http://www.lightbluetouchpaper.org/2007/11/20/wordpress-cookie-authentication-vulnerability/comment-page-1/#comment-27217</link>
		<dc:creator>Steven J. Murdoch</dc:creator>
		<pubDate>Mon, 26 Nov 2007 12:18:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/11/20/wordpress-cookie-authentication-vulnerability/#comment-27217</guid>
		<description>@Abel Cheung

Yes, I&#039;ve been following along on the mailing list. I&#039;m not a member and other list members have already made the points I would have, so I haven&#039;t felt the need to post. For example, I liked &lt;a href=&quot;http://comox.textdrive.com/pipermail/wp-hackers/2007-November/016297.html&quot; rel=&quot;nofollow&quot;&gt;your comment&lt;/a&gt; on how to look at the vulnerability.

I&#039;ve been contributing to a thread on the &lt;a href=&quot;http://trac.wordpress.org/ticket/5367&quot; rel=&quot;nofollow&quot;&gt;bug tracker&lt;/a&gt;. Hopefully the discussion will remain on how to best fix the problem, rather than debating over whether to call it a vulnerability or &lt;a href=&quot;http://comox.textdrive.com/pipermail/wp-hackers/2007-November/016295.html&quot; rel=&quot;nofollow&quot;&gt;&quot;unwanted behavior&quot;&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>@Abel Cheung</p>
<p>Yes, I&#8217;ve been following along on the mailing list. I&#8217;m not a member and other list members have already made the points I would have, so I haven&#8217;t felt the need to post. For example, I liked <a href="http://comox.textdrive.com/pipermail/wp-hackers/2007-November/016297.html" rel="nofollow">your comment</a> on how to look at the vulnerability.</p>
<p>I&#8217;ve been contributing to a thread on the <a href="http://trac.wordpress.org/ticket/5367" rel="nofollow">bug tracker</a>. Hopefully the discussion will remain on how to best fix the problem, rather than debating over whether to call it a vulnerability or <a href="http://comox.textdrive.com/pipermail/wp-hackers/2007-November/016295.html" rel="nofollow">&#8220;unwanted behavior&#8221;</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abel Cheung</title>
		<link>http://www.lightbluetouchpaper.org/2007/11/20/wordpress-cookie-authentication-vulnerability/comment-page-1/#comment-27216</link>
		<dc:creator>Abel Cheung</dc:creator>
		<pubDate>Mon, 26 Nov 2007 12:03:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/11/20/wordpress-cookie-authentication-vulnerability/#comment-27216</guid>
		<description>You&#039;d like to know the &lt;a href=&quot;http://comox.textdrive.com/pipermail/wp-hackers/2007-November/016185.html&quot; rel=&quot;nofollow&quot;&gt;reaction of people in wp-hackers mailing list&lt;/a&gt; as well.

In one sentence: &#039;Bwahahahahahaha. You are senseless. This is not vulnerability.&#039;</description>
		<content:encoded><![CDATA[<p>You&#8217;d like to know the <a href="http://comox.textdrive.com/pipermail/wp-hackers/2007-November/016185.html" rel="nofollow">reaction of people in wp-hackers mailing list</a> as well.</p>
<p>In one sentence: &#8216;Bwahahahahahaha. You are senseless. This is not vulnerability.&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Luz</title>
		<link>http://www.lightbluetouchpaper.org/2007/11/20/wordpress-cookie-authentication-vulnerability/comment-page-1/#comment-27200</link>
		<dc:creator>Daniel Luz</dc:creator>
		<pubDate>Sat, 24 Nov 2007 00:52:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/11/20/wordpress-cookie-authentication-vulnerability/#comment-27200</guid>
		<description>Oh, my. Before reading your posts, I had never looked at Wordpress&#039; source code, and I&#039;m still shocked how such a popular software has an amazingly bad code quality. Definitely, I&#039;m not ever using it for anything.</description>
		<content:encoded><![CDATA[<p>Oh, my. Before reading your posts, I had never looked at Wordpress&#8217; source code, and I&#8217;m still shocked how such a popular software has an amazingly bad code quality. Definitely, I&#8217;m not ever using it for anything.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ndg</title>
		<link>http://www.lightbluetouchpaper.org/2007/11/20/wordpress-cookie-authentication-vulnerability/comment-page-1/#comment-27155</link>
		<dc:creator>ndg</dc:creator>
		<pubDate>Wed, 21 Nov 2007 05:17:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/11/20/wordpress-cookie-authentication-vulnerability/#comment-27155</guid>
		<description>In the past, the attitude of the core WordPress developers towards security has always left something to be desired -- attempts to proactively improve security, including the authentication system, have been shouted down for various reasons (performance, compatibility with ancient versions of PHP, etc.). Last I saw they were still ignoring suggestions to start using parameterized SQL.

Vulnerabilities with exploits in the wild usually get fixed fairly quickly, at least, especially highly public ones. So there&#039;s hope for this one... :)</description>
		<content:encoded><![CDATA[<p>In the past, the attitude of the core WordPress developers towards security has always left something to be desired &#8212; attempts to proactively improve security, including the authentication system, have been shouted down for various reasons (performance, compatibility with ancient versions of PHP, etc.). Last I saw they were still ignoring suggestions to start using parameterized SQL.</p>
<p>Vulnerabilities with exploits in the wild usually get fixed fairly quickly, at least, especially highly public ones. So there&#8217;s hope for this one&#8230; <img src='http://www.lightbluetouchpaper.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Crowley</title>
		<link>http://www.lightbluetouchpaper.org/2007/11/20/wordpress-cookie-authentication-vulnerability/comment-page-1/#comment-27152</link>
		<dc:creator>Paul Crowley</dc:creator>
		<pubDate>Wed, 21 Nov 2007 01:02:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.lightbluetouchpaper.org/2007/11/20/wordpress-cookie-authentication-vulnerability/#comment-27152</guid>
		<description>Someone should write up a proper description of how to do this kind of website password security in one place.  How to store a password.  How to generate an authentication cookie when someone logs in.  Whether to stretch passwords.  How to use an email address to handle the situation where a user forgets their password (so many sites get this wrong in so many ways).  And so on.

Bad practice in this area is I&#039;m sure far more common than good.  Many web applications still email you your password as soon as you set it!</description>
		<content:encoded><![CDATA[<p>Someone should write up a proper description of how to do this kind of website password security in one place.  How to store a password.  How to generate an authentication cookie when someone logs in.  Whether to stretch passwords.  How to use an email address to handle the situation where a user forgets their password (so many sites get this wrong in so many ways).  And so on.</p>
<p>Bad practice in this area is I&#8217;m sure far more common than good.  Many web applications still email you your password as soon as you set it!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

