<?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: PHP sessions on shared hosting &#8211; Hack It! #3</title>
	<atom:link href="http://www.supernifty.com.au/blog/2008/04/19/php-sessions-on-shared-hosting-hack-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.supernifty.com.au/blog/2008/04/19/php-sessions-on-shared-hosting-hack-3/</link>
	<description>that is also super</description>
	<lastBuildDate>Sun, 29 Jan 2012 02:50:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: peter</title>
		<link>http://www.supernifty.com.au/blog/2008/04/19/php-sessions-on-shared-hosting-hack-3/comment-page-1/#comment-4581</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Sun, 08 Feb 2009 01:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.supernifty.com.au/blog/2008/04/19/php-sessions-on-shared-hosting-hack-3/#comment-4581</guid>
		<description>Hey Harry,

If at all possible, don&#039;t put your sessions under your www directory - as you said, this exposes them to the outside world. Not good!

If you must put your session directory under www, definitely password protect it with htaccess. There&#039;s probably even a &quot;no access&quot; directive you can put in your .htaccess file.</description>
		<content:encoded><![CDATA[<p>Hey Harry,</p>
<p>If at all possible, don&#8217;t put your sessions under your www directory &#8211; as you said, this exposes them to the outside world. Not good!</p>
<p>If you must put your session directory under www, definitely password protect it with htaccess. There&#8217;s probably even a &#8220;no access&#8221; directive you can put in your .htaccess file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: harry</title>
		<link>http://www.supernifty.com.au/blog/2008/04/19/php-sessions-on-shared-hosting-hack-3/comment-page-1/#comment-4577</link>
		<dc:creator>harry</dc:creator>
		<pubDate>Fri, 23 Jan 2009 14:50:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.supernifty.com.au/blog/2008/04/19/php-sessions-on-shared-hosting-hack-3/#comment-4577</guid>
		<description>sweet, after reading for hours, this helps clear up a lot.

my only question, with this hack, i am now moving my session files to a www/ folder. i can password protect it i guess, but it is now open to public hacking.

do you know what safeguards i can use in this case?</description>
		<content:encoded><![CDATA[<p>sweet, after reading for hours, this helps clear up a lot.</p>
<p>my only question, with this hack, i am now moving my session files to a www/ folder. i can password protect it i guess, but it is now open to public hacking.</p>
<p>do you know what safeguards i can use in this case?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

