<?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 v3</title>
	<atom:link href="http://moggy.laceous.com/2009/09/05/semisecure-login-reimagined-v3/feed/" rel="self" type="application/rss+xml" />
	<link>http://moggy.laceous.com/2009/09/05/semisecure-login-reimagined-v3/</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: moggy</title>
		<link>http://moggy.laceous.com/2009/09/05/semisecure-login-reimagined-v3/comment-page-1/#comment-237</link>
		<dc:creator>moggy</dc:creator>
		<pubDate>Thu, 04 Mar 2010 03:06:02 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=223#comment-237</guid>
		<description>Do you have a phpinfo page? Does it list openssl?  If not, it&#039;s possible to install &lt;a href=&quot;http://www.google.com/search?q=openssl+windows&quot; rel=&quot;nofollow&quot;&gt;openssl on windows&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Do you have a phpinfo page? Does it list openssl?  If not, it&#8217;s possible to install <a href="http://www.google.com/search?q=openssl+windows" rel="nofollow">openssl on windows</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micah</title>
		<link>http://moggy.laceous.com/2009/09/05/semisecure-login-reimagined-v3/comment-page-1/#comment-236</link>
		<dc:creator>Micah</dc:creator>
		<pubDate>Mon, 01 Mar 2010 21:14:53 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=223#comment-236</guid>
		<description>Does this plugin not work with Windows servers? It&#039;s referencing
OpenSSL but I&#039;m guessing that this is only installed on Unix-based
servers. When I tried to activate this on a Windows server with
Wordpress, it would not properly activate since it couldn&#039;t use
OpenSSL.</description>
		<content:encoded><![CDATA[<p>Does this plugin not work with Windows servers? It&#8217;s referencing<br />
OpenSSL but I&#8217;m guessing that this is only installed on Unix-based<br />
servers. When I tried to activate this on a Windows server with<br />
Wordpress, it would not properly activate since it couldn&#8217;t use<br />
OpenSSL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chantak</title>
		<link>http://moggy.laceous.com/2009/09/05/semisecure-login-reimagined-v3/comment-page-1/#comment-231</link>
		<dc:creator>Chantak</dc:creator>
		<pubDate>Sun, 10 Jan 2010 17:37:39 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=223#comment-231</guid>
		<description>Can you add the Poly1305-AES encryption in your plugin? The link
is: http://cr.yp.to/mac.html</description>
		<content:encoded><![CDATA[<p>Can you add the Poly1305-AES encryption in your plugin? The link<br />
is: <a href="http://cr.yp.to/mac.html" rel="nofollow">http://cr.yp.to/mac.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micah</title>
		<link>http://moggy.laceous.com/2009/09/05/semisecure-login-reimagined-v3/comment-page-1/#comment-230</link>
		<dc:creator>Micah</dc:creator>
		<pubDate>Thu, 24 Dec 2009 20:47:35 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=223#comment-230</guid>
		<description>I actually did set the nonces option to async and that didn&#039;t work.
I tried to disable nonce and that seemed to actually work on
initial testing. The error I was getting after trying to log in was
a red block above the log in fields saying, &quot;The password field is
empty.&quot; over and over. Of course this was false since I had a
password in there every time.</description>
		<content:encoded><![CDATA[<p>I actually did set the nonces option to async and that didn&#8217;t work.<br />
I tried to disable nonce and that seemed to actually work on<br />
initial testing. The error I was getting after trying to log in was<br />
a red block above the log in fields saying, &#8220;The password field is<br />
empty.&#8221; over and over. Of course this was false since I had a<br />
password in there every time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: moggy</title>
		<link>http://moggy.laceous.com/2009/09/05/semisecure-login-reimagined-v3/comment-page-1/#comment-229</link>
		<dc:creator>moggy</dc:creator>
		<pubDate>Thu, 24 Dec 2009 15:22:53 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=223#comment-229</guid>
		<description>@Micah -- Thanks for the report. If you disable JavaScript in your browser you should be able to log in (without encryption). I&#039;ve never used that specific caching plugin, but you might need to set nonces to use the async option. You could also try disabling nonces.</description>
		<content:encoded><![CDATA[<p>@Micah &#8212; Thanks for the report. If you disable JavaScript in your browser you should be able to log in (without encryption). I&#8217;ve never used that specific caching plugin, but you might need to set nonces to use the async option. You could also try disabling nonces.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micah</title>
		<link>http://moggy.laceous.com/2009/09/05/semisecure-login-reimagined-v3/comment-page-1/#comment-228</link>
		<dc:creator>Micah</dc:creator>
		<pubDate>Thu, 24 Dec 2009 05:00:15 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=223#comment-228</guid>
		<description>Hey moggy, after installing Wordpress 2.9 and this plugin, I had
trouble logging back in when I later tried to log back in. The
resolution was to delete this plugin from the plugins folder. The
only other active plugins I had were WP Total Cache and Akismet.
Just a FYI in case you hear anything else.</description>
		<content:encoded><![CDATA[<p>Hey moggy, after installing Wordpress 2.9 and this plugin, I had<br />
trouble logging back in when I later tried to log back in. The<br />
resolution was to delete this plugin from the plugins folder. The<br />
only other active plugins I had were WP Total Cache and Akismet.<br />
Just a FYI in case you hear anything else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: moggy</title>
		<link>http://moggy.laceous.com/2009/09/05/semisecure-login-reimagined-v3/comment-page-1/#comment-227</link>
		<dc:creator>moggy</dc:creator>
		<pubDate>Thu, 17 Dec 2009 10:02:41 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=223#comment-227</guid>
		<description>@Viper -- I&#039;ll consider it for a future version. I always liked the way that the original plugin let you disable JavaScript to log in without encryption (something that I kept for this reimagined version).  IMO, that was one of the selling points for using it over Chap Secure Login.</description>
		<content:encoded><![CDATA[<p>@Viper &#8212; I&#8217;ll consider it for a future version. I always liked the way that the original plugin let you disable JavaScript to log in without encryption (something that I kept for this reimagined version).  IMO, that was one of the selling points for using it over Chap Secure Login.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Viper007Bond</title>
		<link>http://moggy.laceous.com/2009/09/05/semisecure-login-reimagined-v3/comment-page-1/#comment-226</link>
		<dc:creator>Viper007Bond</dc:creator>
		<pubDate>Sat, 05 Dec 2009 12:43:39 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=223#comment-226</guid>
		<description>Thanks for the great plugin! I&#039;d love an option that somehow made
it impossible to log in without using this. Perhaps removing the
login fields and adding them back using Javascript or something.
That way a password will never be sent in the clear ever.</description>
		<content:encoded><![CDATA[<p>Thanks for the great plugin! I&#8217;d love an option that somehow made<br />
it impossible to log in without using this. Perhaps removing the<br />
login fields and adding them back using Javascript or something.<br />
That way a password will never be sent in the clear ever.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Secure WordPress login without HTTPS &#124; Blinkenlichten Blog</title>
		<link>http://moggy.laceous.com/2009/09/05/semisecure-login-reimagined-v3/comment-page-1/#comment-225</link>
		<dc:creator>Secure WordPress login without HTTPS &#124; Blinkenlichten Blog</dc:creator>
		<pubDate>Mon, 16 Nov 2009 05:41:14 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=223#comment-225</guid>
		<description>[...] WordPress version: 2.7 or higher Tested with WordPress
version: 2.8.6 by me Plugin homepage link: Moggy’s
Website/Semisecure Login Reimagined v3 Author homepage link: [...]</description>
		<content:encoded><![CDATA[<p>[...] WordPress version: 2.7 or higher Tested with WordPress<br />
version: 2.8.6 by me Plugin homepage link: Moggy’s<br />
Website/Semisecure Login Reimagined v3 Author homepage link: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Top 1000 WordPress Plugin Authors &#171; Metode de promovare</title>
		<link>http://moggy.laceous.com/2009/09/05/semisecure-login-reimagined-v3/comment-page-1/#comment-224</link>
		<dc:creator>Top 1000 WordPress Plugin Authors &#171; Metode de promovare</dc:creator>
		<pubDate>Fri, 06 Nov 2009 18:59:47 +0000</pubDate>
		<guid isPermaLink="false">http://moggy.laceous.com/?p=223#comment-224</guid>
		<description>[...] Semisecure Login Reimagined [...]</description>
		<content:encoded><![CDATA[<p>[...] Semisecure Login Reimagined [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
