<?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: Drupal login and SSL</title>
	<atom:link href="http://kire.notneb.net/archives/10/feed" rel="self" type="application/rss+xml" />
	<link>http://kire.notneb.net/archives/10</link>
	<description>On the bleeding edge of yesterday.</description>
	<lastBuildDate>Wed, 07 Dec 2011 21:31:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Josh</title>
		<link>http://kire.notneb.net/archives/10/comment-page-1#comment-43</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Mon, 13 Jul 2009 02:04:26 +0000</pubDate>
		<guid isPermaLink="false">http://kire.notneb.net/?p=10#comment-43</guid>
		<description>Thanks for the post, it was helpful.

I noticed a typo, the last line should be RewriteRule instead of RewriteCond</description>
		<content:encoded><![CDATA[<p>Thanks for the post, it was helpful.</p>
<p>I noticed a typo, the last line should be RewriteRule instead of RewriteCond</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik</title>
		<link>http://kire.notneb.net/archives/10/comment-page-1#comment-31</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Tue, 28 Oct 2008 16:19:32 +0000</pubDate>
		<guid isPermaLink="false">http://kire.notneb.net/?p=10#comment-31</guid>
		<description>Arian,
Thanks for your comment. You win the cookie for the first real comment here. I&#039;ll also look into the cookie differences. I too noticed that the cookie session is valid for both SSL and non-SSL sessions, which I agree is a pretty big problem. I&#039;ll follow up on your links after a bit more research.

Thanks again.</description>
		<content:encoded><![CDATA[<p>Arian,<br />
Thanks for your comment. You win the cookie for the first real comment here. I&#8217;ll also look into the cookie differences. I too noticed that the cookie session is valid for both SSL and non-SSL sessions, which I agree is a pretty big problem. I&#8217;ll follow up on your links after a bit more research.</p>
<p>Thanks again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arian</title>
		<link>http://kire.notneb.net/archives/10/comment-page-1#comment-30</link>
		<dc:creator>Arian</dc:creator>
		<pubDate>Tue, 28 Oct 2008 15:42:44 +0000</pubDate>
		<guid isPermaLink="false">http://kire.notneb.net/?p=10#comment-30</guid>
		<description>Doing mixed ssl/non-ssl session via Secure Pages module or writing your own mod_rewrites think there is an outstanding issue with drupal mixed sessions. When use ssl/and non-ssl for other pages, the secure session cookie isnt secure after the login, as it will be used in the non-ssl pages.
One might set php&#039;s session.cookie_secure sends cookies only over secure connections, but that means after logging in and going back to http, the cookie isnt transfered and user is anonymous, i think breaking any community functionality.

seems like one solution is to use ssl on whole site. another is to use Secure Pages patch listed on 2nd site, so ssl uses ssl cookie, and non-sll sends another cookie over network.

http://heine.familiedeelstra.com/security-theater-dail-ssl-for-login
http://www.opensourcery.com/blog/dylan-tack/improving-security-drupals-securepages-module</description>
		<content:encoded><![CDATA[<p>Doing mixed ssl/non-ssl session via Secure Pages module or writing your own mod_rewrites think there is an outstanding issue with drupal mixed sessions. When use ssl/and non-ssl for other pages, the secure session cookie isnt secure after the login, as it will be used in the non-ssl pages.<br />
One might set php&#8217;s session.cookie_secure sends cookies only over secure connections, but that means after logging in and going back to http, the cookie isnt transfered and user is anonymous, i think breaking any community functionality.</p>
<p>seems like one solution is to use ssl on whole site. another is to use Secure Pages patch listed on 2nd site, so ssl uses ssl cookie, and non-sll sends another cookie over network.</p>
<p><a href="http://heine.familiedeelstra.com/security-theater-dail-ssl-for-login" rel="nofollow">http://heine.familiedeelstra.com/security-theater-dail-ssl-for-login</a><br />
<a href="http://www.opensourcery.com/blog/dylan-tack/improving-security-drupals-securepages-module" rel="nofollow">http://www.opensourcery.com/blog/dylan-tack/improving-security-drupals-securepages-module</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

