<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wordpress on System Overlord</title><link>https://systemoverlord.com/tags/wordpress.html</link><description>Recent content in Wordpress on System Overlord</description><generator>Hugo</generator><language>en-us</language><managingEditor>david@systemoverlord.com (David Tomaschik)</managingEditor><webMaster>david@systemoverlord.com (David Tomaschik)</webMaster><lastBuildDate>Wed, 10 Sep 2014 22:54:52 +0000</lastBuildDate><atom:link href="https://systemoverlord.com/tags/wordpress/index.xml" rel="self" type="application/rss+xml"/><item><title>[CVE-2014-5204] Wordpress nonce Issues</title><link>https://systemoverlord.com/2014/09/10/cve-2014-5204-wordpress-nonce-issues/</link><pubDate>Wed, 10 Sep 2014 22:54:52 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2014/09/10/cve-2014-5204-wordpress-nonce-issues/</guid><description>&lt;p&gt;Wordpress 3.9.2, released August 6th, contained fixes for two closely related
vulnerabilities (CVE-2014-5204) in the way it handles Wordpress nonces (CSRF
Tokens, essentially) that I reported to the Wordpress Security Team. I&amp;rsquo;d like
to say the delay in my publishing this write-up was to allow people time to
patch, but the reality is I&amp;rsquo;ve just been busy and haven&amp;rsquo;t gotten around to this.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; Wordpress &amp;lt; 3.9.2 generated nonces in a manner that would allow an
attacker to generate valid nonces for other users for a &lt;strong&gt;small&lt;/strong&gt; subset of
possible actions. Additionally, nonces were compared with &lt;code&gt;==&lt;/code&gt;, leading to a
timing attack against nonce comparison. (Although this is very difficult to
execute.)&lt;/p&gt;</description></item><item><title>Welcome (back) to Drupal!</title><link>https://systemoverlord.com/2011/03/23/welcome-back-to-drupal/</link><pubDate>Wed, 23 Mar 2011 01:21:23 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2011/03/23/welcome-back-to-drupal/</guid><description>&lt;p&gt;
	Regular readers of my blog may have noticed a significant change.  As of about midnight last night, I had completed the migration of my site from Wordpress 3.1 to Drupal 7.  A few features are not yet implemented, including automatically posting my blog entries to Twitter, but the RSS feeds do work.  Additionally, some of the RSS feed URLs have changed, so please check your feed readers.&lt;/p&gt;</description></item><item><title>Welcome to Nginx!</title><link>https://systemoverlord.com/2011/01/23/welcome-to-nginx/</link><pubDate>Sun, 23 Jan 2011 17:49:21 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2011/01/23/welcome-to-nginx/</guid><description>&lt;p&gt;If you're reading this, it's thanks to Nginx.  As of about midnight last night, all content on SystemOverlord.com is being served up by Nginx.  I did this for two reasons: Nginx has a much smaller memory profile than Apache, which is important when running on a 512MB VPS, and Nginx's preferred PHP path is through a FastCGI interface, which allows me to run separate PHP FastCGIs under different users for each application on my server.  Privilege separation for different webapps has always been a big thing security-wise, and I'm glad I was able to get it going with a minimum of fuss.  &lt;a href="http://wordpress.org"&gt;Wordpress&lt;/a&gt;, &lt;a href="http://nginx.org"&gt;Nginx&lt;/a&gt;, &lt;a href="http://mysql.com"&gt;MySQL&lt;/a&gt;, and &lt;a href="http://ubuntu.com"&gt;Ubuntu Server&lt;/a&gt; powered, all on a &lt;a href="http://www.linode.com/?r=680a893e24df3597d32f58cd41930e969027dc06"&gt;Linode VPS&lt;/a&gt;!&lt;/p&gt;</description></item></channel></rss>