<?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>Blinkenlichten Blog &#187; Tutorials</title>
	<atom:link href="http://blinkenlichten.org/blog/categories/tutorials/feed/" rel="self" type="application/rss+xml" />
	<link>http://blinkenlichten.org/blog</link>
	<description>A hilarious insight into the life of P.W.</description>
	<lastBuildDate>Sat, 24 Jul 2010 04:55:29 +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>Secure WordPress login without HTTPS</title>
		<link>http://blinkenlichten.org/blog/2009/11/16/secure-wordpress-login-without-https/</link>
		<comments>http://blinkenlichten.org/blog/2009/11/16/secure-wordpress-login-without-https/#comments</comments>
		<pubDate>Mon, 16 Nov 2009 05:41:03 +0000</pubDate>
		<dc:creator>Pat</dc:creator>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[planet.cosi.clarkson.edu]]></category>
		<category><![CDATA[blogging]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://blinkenlichten.org/blog/?p=104</guid>
		<description><![CDATA[Do you access a WordPress installation on a web server without HTTPS? If so, your passwords are sent in plaintext every time you login, register for accounts, add new users through the admin interface, and change user passwords. Unfortunately, if you use a professional web host, there is a good chance that you are stuck [...]]]></description>
			<content:encoded><![CDATA[<p>Do you access a WordPress installation on a web server without HTTPS?  If so, your passwords are sent in plaintext every time you login, register for accounts, add new users through the admin interface, and change user passwords.</p>
<p>Unfortunately, if you use a professional web host, there is a good chance that you are stuck in a situation where you use WordPress for your blog or website but cannot use HTTPS to secure your access to your WordPress installation.  This can be caused by anything, such as: HTTPS is simply not offered, HTTPS costs quite a bit extra to have enabled, your WordPress installation is in a shared hosting environment, or multiple domains you own are tied to your hosting account in a way that complicates the issuing of certificates and setup of HTTPS.</p>
<p>Fortunately, there is a solution (actually, one of many) for WordPress fans to improve the sending of passwords over HTTP.</p>
<p><a href="http://wordpress.org/extend/plugins/semisecure-login-reimagined/">Semisecure Login Reimagined</a> is a plugin for WordPress that implements client-side (browser-side) encryption in JavaScript, complete with the use of nonces to prevent against replay attacks (note that this plugin is NOT designed to necessarily protect against session hijacking).  <strong>My installation instructions are at the bottom of this post.</strong></p>
<p><strong>Plugin Details:</strong><br />
<em>About link: </em> <a href="http://wordpress.org/extend/plugins/semisecure-login-reimagined/">WordPress Plugins Directory/Semisecure Login Reimagined</a><br />
<em>Requires WordPress version:</em> 2.7 or higher<br />
<em>Tested with WordPress version:</em> 2.8.6 by me<br />
<em>Plugin homepage link:</em> <a href="http://moggy.laceous.com/2009/09/05/semisecure-login-reimagined-v3/">Moggy&#8217;s Website/Semisecure Login Reimagined v3</a><br />
<em>Author homepage link:</em> <a href="http://moggy.laceous.com/">Moggy</a></p>
<p>Description of plugin from the WordPress plugin directory:</p>
<blockquote><p>&#8220;Semisecure Login Reimagined increases the security of the login process by using a combination of public and secret-key encryption to encrypt the password on the client-side when a user logs in. JavaScript is required to enable encryption. It is most useful for situations where SSL is not available, but the administrator wishes to have some additional security measures in place without sacrificing convenience.&#8221;</p></blockquote>
<p><strong>Automatic installation instructions:</strong></p>
<ol>
<li>Login to your WordPress installation through the admin interface as one of your administrator-privileged users (<em>http://your-site-url-here/wp-admin/</em>), and be sure to do this from a trusted, non-public Internet connection, on a private network and not over a wireless connection.</li>
<li>Click on <em>Plugins</em> on the left navigation bar.</li>
<li>With Plugins selected, there should now be an <em>Add New</em> link just beneath Plugins in the left navigation bar.  Click on <em>Add New</em> just beneath the word Plugins.</li>
<li>On the Install Plugins page under Search, be sure that <em>Term</em> appears in the drop-down (else click the drop-down arrow and select <em>Term</em>) and then enter in the search box to the right of Term &#8220;semisecure login reimagined&#8221; exactly as shown (but without the quotes).  Click <em>Search Plugins</em>.</li>
<li>In the search results, Semisecure Login Reimagined should appear.  All the way on the right-side of that result should be an <em>Install</em> link.  Click on <em>Install</em>.</li>
<li>In the box that appears, click on the (red) <em>Install Now</em> button.</li>
<li>On the results page, click on <em>Activate Plugin</em>.  You now have secure login wherever available, but we can do better (so keep reading the following steps).</li>
<li>Click on <em>Plugins</em> on the left navigation bar.</li>
<li>Under Semisecure Login Reimagined, click <em>Settings</em> to edit that plugin&#8217;s settings.</li>
<li>Note the Wikipedia quote stating, &#8220;RSA claims that 1024-bit keys are likely to become crackable some time between 2006 and 2010 and that 2048-bit keys are sufficient until 2030. An RSA key length of 3072 bits should be used if security is required beyond 2030.&#8221;  In the <em>Number of bits</em> drop-down, select the number of bits you wish for the encryption to use.  1024 is the default (faster performance) but is likely to be easily-crackable by the end of 2010, 2048 is considerably better at present, and 3072 might be even better (but will have slower performance).  You should pick what you feel most comfortable with, or if you are unsure and this is for a blog that you and possibly a few others manage I would recommend picking 2048 for better security and a slight performance decrease (only during authentication).</li>
<li>Click the <em>Generate Key</em> button.</li>
<li>Click <em>Misc Settings</em> up near the top of the page.</li>
<li>Check the box next to <em>Encrypt passwords when managing users?</em>.  Congratulations! Now not only are your initial login passwords encrypted, but also passwords entered when adding new users, changing passwords, etc.</li>
<li><em>(If you experience problems logging in, likely due to caching issues, set the Nonce setting to Asynch (Ajax). Otherwise, you can probably just leave this setting as-is.)</em></li>
<li>Click the <em>Update Option</em>s button.</li>
</ol>
<p>Log out, log back in, and on the login page you should see a little message stating, &#8220;Semisecure Login is enabled,&#8221; just below the Password entry box. Congratulations, your passwords are no longer being sent in plaintext!</p>
<p>If you like this tutorial, please share it with others, link to this post, and let me know!</p>
]]></content:encoded>
			<wfw:commentRss>http://blinkenlichten.org/blog/2009/11/16/secure-wordpress-login-without-https/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
