<?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"
	>
<channel>
	<title>Comments on: HOWTO create your blog - anonymously</title>
	<atom:link href="http://livelyblog.com/archives/4/feed" rel="self" type="application/rss+xml" />
	<link>http://livelyblog.com/archives/4</link>
	<description>Get your own free personal blog</description>
	<pubDate>Thu, 08 Jan 2009 13:41:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: admin</title>
		<link>http://livelyblog.com/archives/4#comment-38</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sun, 15 Apr 2007 23:58:25 +0000</pubDate>
		<guid isPermaLink="false">http://livelyblog.com/2006/10/09/howto-create-your-blog-anonymously/#comment-38</guid>
		<description>It did for a while. And it will if we find out how to do it securely. WordPress MU is absolutely not made to be served over https. It is possible to change core files to make it login using https, but there are a whole lot of issues which makes https much less secure than it should be. If you login using https and your browser sometimes makes plaintext connections which sends the session cookie then you're just as unsecure as if you were not using https at all.

The reason https is turned off alltogether right now is that we do not want to give you a false sense of security. Half-secure https gives you the impression that your connection remains encrypted when in fact it's not, so https won't be available until or unless we find out how to do it in a way that is really secure.</description>
		<content:encoded><![CDATA[<p>It did for a while. And it will if we find out how to do it securely. WordPress MU is absolutely not made to be served over https. It is possible to change core files to make it login using https, but there are a whole lot of issues which makes https much less secure than it should be. If you login using https and your browser sometimes makes plaintext connections which sends the session cookie then you&#8217;re just as unsecure as if you were not using https at all.</p>
<p>The reason https is turned off alltogether right now is that we do not want to give you a false sense of security. Half-secure https gives you the impression that your connection remains encrypted when in fact it&#8217;s not, so https won&#8217;t be available until or unless we find out how to do it in a way that is really secure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kranjal</title>
		<link>http://livelyblog.com/archives/4#comment-35</link>
		<dc:creator>kranjal</dc:creator>
		<pubDate>Fri, 30 Mar 2007 04:10:21 +0000</pubDate>
		<guid isPermaLink="false">http://livelyblog.com/2006/10/09/howto-create-your-blog-anonymously/#comment-35</guid>
		<description>I thought livelyblog used ssl encryption between the user and the server.</description>
		<content:encoded><![CDATA[<p>I thought livelyblog used ssl encryption between the user and the server.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
