<?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: Semisecure Login Reimagined</title>
	<atom:link href="http://moggy.laceous.com/2008/05/30/semisecure-login-reimagined/feed/" rel="self" type="application/rss+xml" />
	<link>http://moggy.laceous.com/2008/05/30/semisecure-login-reimagined/</link>
	<description>If nothing we do matters, then all that matters is what we do.</description>
	<lastBuildDate>Thu, 04 Mar 2010 03:06:02 -0800</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Wordpress security dissected and analyzed: Part 2 &#124; Bandit Defense</title>
		<link>http://moggy.laceous.com/2008/05/30/semisecure-login-reimagined/comment-page-1/#comment-140</link>
		<dc:creator>Wordpress security dissected and analyzed: Part 2 &#124; Bandit Defense</dc:creator>
		<pubDate>Tue, 28 Apr 2009 08:27:53 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=51#comment-140</guid>
		<description>[...] you don’t have an SSL certificate on your server, Semisecure
Login Reimagined is a wonderful plugin. I explained its usefulness
in a previous [...]</description>
		<content:encoded><![CDATA[<p>[...] you don’t have an SSL certificate on your server, Semisecure<br />
Login Reimagined is a wonderful plugin. I explained its usefulness<br />
in a previous [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: moggy</title>
		<link>http://moggy.laceous.com/2008/05/30/semisecure-login-reimagined/comment-page-1/#comment-136</link>
		<dc:creator>moggy</dc:creator>
		<pubDate>Mon, 16 Mar 2009 07:25:12 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=51#comment-136</guid>
		<description>Sorry about that.  Looks like there was a typo.  I just pushed an update to fix the issue.</description>
		<content:encoded><![CDATA[<p>Sorry about that.  Looks like there was a typo.  I just pushed an update to fix the issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Álvaro Degives-Más</title>
		<link>http://moggy.laceous.com/2008/05/30/semisecure-login-reimagined/comment-page-1/#comment-135</link>
		<dc:creator>Álvaro Degives-Más</dc:creator>
		<pubDate>Sun, 15 Mar 2009 06:16:22 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=51#comment-135</guid>
		<description>Scratch that... I installed the previous version (1.4.0) created
the keys, upgraded to the current, problem solved. :-) Works like a
charm. Thanks!</description>
		<content:encoded><![CDATA[<p>Scratch that&#8230; I installed the previous version (1.4.0) created<br />
the keys, upgraded to the current, problem solved. :-) Works like a<br />
charm. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Álvaro Degives-Más</title>
		<link>http://moggy.laceous.com/2008/05/30/semisecure-login-reimagined/comment-page-1/#comment-134</link>
		<dc:creator>Álvaro Degives-Más</dc:creator>
		<pubDate>Sat, 14 Mar 2009 22:49:21 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=51#comment-134</guid>
		<description>Hi Moggy, the plugin is really awesome. Thanks so much! I have a WP
based site I maintain for a non-profit, which gives me a puzzling
error upon activation of the plugin:
&lt;blockquote&gt;
  Parse error: syntax error, unexpected &#039;;&#039;, expecting &#039;)&#039; in
  /[path-to]/public_html/wp-content/plugins/semisecure-login-reimagined/SemisecureLoginReimagined_RsaKeys.php
  on line 73
&lt;/blockquote&gt;I can&#039;t figure out what&#039;s going wrong there... It
activates, but seemingly won&#039;t generate the keys, no matter the
setting I choose. Could you point me in the right direction?
Server&#039;s running PHP5.2... Dunno what other info might be helpful
to you. Thanks in advance!</description>
		<content:encoded><![CDATA[<p>Hi Moggy, the plugin is really awesome. Thanks so much! I have a WP<br />
based site I maintain for a non-profit, which gives me a puzzling<br />
error upon activation of the plugin:</p>
<blockquote><p>
  Parse error: syntax error, unexpected &#8216;;&#8217;, expecting &#8216;)&#8217; in<br />
  /[path-to]/public_html/wp-content/plugins/semisecure-login-reimagined/SemisecureLoginReimagined_RsaKeys.php<br />
  on line 73
</p></blockquote>
<p>I can&#8217;t figure out what&#8217;s going wrong there&#8230; It<br />
activates, but seemingly won&#8217;t generate the keys, no matter the<br />
setting I choose. Could you point me in the right direction?<br />
Server&#8217;s running PHP5.2&#8230; Dunno what other info might be helpful<br />
to you. Thanks in advance!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JeKoPhoto</title>
		<link>http://moggy.laceous.com/2008/05/30/semisecure-login-reimagined/comment-page-1/#comment-133</link>
		<dc:creator>JeKoPhoto</dc:creator>
		<pubDate>Mon, 09 Mar 2009 18:40:40 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=51#comment-133</guid>
		<description>Moggy, thanks for pointing that out - I was not be aware of this by
now. In fact it would be sensless in this circumstances to en- and
decrypt the username. Thanks again, Jens</description>
		<content:encoded><![CDATA[<p>Moggy, thanks for pointing that out &#8211; I was not be aware of this by<br />
now. In fact it would be sensless in this circumstances to en- and<br />
decrypt the username. Thanks again, Jens</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: moggy</title>
		<link>http://moggy.laceous.com/2008/05/30/semisecure-login-reimagined/comment-page-1/#comment-132</link>
		<dc:creator>moggy</dc:creator>
		<pubDate>Mon, 09 Mar 2009 07:53:47 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=51#comment-132</guid>
		<description>Jens - 
The default cookie(s) that WordPress uses stores your username as plain-text.  So there&#039;s no point in encrypting the username when logging in since it&#039;s going to be sent &quot;over the wire&quot; 3 seconds later anyway.</description>
		<content:encoded><![CDATA[<p>Jens &#8211;<br />
The default cookie(s) that WordPress uses stores your username as plain-text.  So there&#8217;s no point in encrypting the username when logging in since it&#8217;s going to be sent &#8220;over the wire&#8221; 3 seconds later anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: m0rebel</title>
		<link>http://moggy.laceous.com/2008/05/30/semisecure-login-reimagined/comment-page-1/#comment-131</link>
		<dc:creator>m0rebel</dc:creator>
		<pubDate>Mon, 09 Mar 2009 02:12:12 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=51#comment-131</guid>
		<description>I recently discovered this plugin and it&#039;s awesome! I have a
computer security blog and I just wrote a post recommending it.
Check it out:
http://blog.banditdefense.com/2009/03/08/wordpress-password-security-on-a-budget/</description>
		<content:encoded><![CDATA[<p>I recently discovered this plugin and it&#8217;s awesome! I have a<br />
computer security blog and I just wrote a post recommending it.<br />
Check it out:<br />
<a href="http://blog.banditdefense.com/2009/03/08/wordpress-password-security-on-a-budget/" rel="nofollow">http://blog.banditdefense.com/2009/03/08/wordpress-password-security-on-a-budget/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wordpress password security on a budget &#124; Bandit Defense</title>
		<link>http://moggy.laceous.com/2008/05/30/semisecure-login-reimagined/comment-page-1/#comment-130</link>
		<dc:creator>Wordpress password security on a budget &#124; Bandit Defense</dc:creator>
		<pubDate>Mon, 09 Mar 2009 02:01:52 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=51#comment-130</guid>
		<description>[...] the Semisecure Login Reimagined Wordpress plugin. If you
can’t afford SSL for your website, this is your next best bet. On
[...]</description>
		<content:encoded><![CDATA[<p>[...] the Semisecure Login Reimagined Wordpress plugin. If you<br />
can’t afford SSL for your website, this is your next best bet. On<br />
[...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JeKoPhoto</title>
		<link>http://moggy.laceous.com/2008/05/30/semisecure-login-reimagined/comment-page-1/#comment-128</link>
		<dc:creator>JeKoPhoto</dc:creator>
		<pubDate>Tue, 03 Mar 2009 18:16:33 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=51#comment-128</guid>
		<description>Moggy, first I want to thank you for this great plugin! It is a
really good choice for those who are not able to use ssl. Did you
thought about encrypting the username too? I think this could
improve the level of security. So there would be absolutely no
login information which goes unencrypted through the net and an
possible attacker did not know the half of the needed information
;-) Would be interested what you are thinking about. Cheers, Jens</description>
		<content:encoded><![CDATA[<p>Moggy, first I want to thank you for this great plugin! It is a<br />
really good choice for those who are not able to use ssl. Did you<br />
thought about encrypting the username too? I think this could<br />
improve the level of security. So there would be absolutely no<br />
login information which goes unencrypted through the net and an<br />
possible attacker did not know the half of the needed information<br />
;-) Would be interested what you are thinking about. Cheers, Jens</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Les extensions WordPress de Mind Overflow &#124; Mind Overflow</title>
		<link>http://moggy.laceous.com/2008/05/30/semisecure-login-reimagined/comment-page-1/#comment-103</link>
		<dc:creator>Les extensions WordPress de Mind Overflow &#124; Mind Overflow</dc:creator>
		<pubDate>Mon, 29 Dec 2008 19:27:58 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=51#comment-103</guid>
		<description>[...] Semisecure Login Reimagined (1.4.0) : permet de chiffrer
certains éléments du blog grâce à un système de clé privée/clé
publique basé sur le RSA. [...]</description>
		<content:encoded><![CDATA[<p>[...] Semisecure Login Reimagined (1.4.0) : permet de chiffrer<br />
certains éléments du blog grâce à un système de clé privée/clé<br />
publique basé sur le RSA. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
