<?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: Tweet Week: Sept 28-Oct 4, 2009</title>
	<atom:link href="http://blog.unmaskparasites.com/2009/10/04/tweet-week-sept-28-oct-4-2009/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.unmaskparasites.com/2009/10/04/tweet-week-sept-28-oct-4-2009/</link>
	<description>Website insecurity by example</description>
	<lastBuildDate>Fri, 03 Sep 2010 20:05:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: MK</title>
		<link>http://blog.unmaskparasites.com/2009/10/04/tweet-week-sept-28-oct-4-2009/comment-page-1/#comment-4540</link>
		<dc:creator>MK</dc:creator>
		<pubDate>Tue, 06 Oct 2009 11:12:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.unmaskparasites.com/?p=332#comment-4540</guid>
		<description>This is correct. Since a particular user has ownership over all of their own files, they will always have the necessary permissions in order to edit them (or at least can change the permissions to necessary value in order to edit). 

I&#039;ve not had a chance to examine the Beladen/Goscanpark malware in any detail as of yet. However, from the information I have read on these, they rely on Apache and PHP running under the same user in order to modify it&#039;s responses.</description>
		<content:encoded><![CDATA[<p>This is correct. Since a particular user has ownership over all of their own files, they will always have the necessary permissions in order to edit them (or at least can change the permissions to necessary value in order to edit). </p>
<p>I&#8217;ve not had a chance to examine the Beladen/Goscanpark malware in any detail as of yet. However, from the information I have read on these, they rely on Apache and PHP running under the same user in order to modify it&#8217;s responses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Denis</title>
		<link>http://blog.unmaskparasites.com/2009/10/04/tweet-week-sept-28-oct-4-2009/comment-page-1/#comment-4537</link>
		<dc:creator>Denis</dc:creator>
		<pubDate>Tue, 06 Oct 2009 09:03:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.unmaskparasites.com/?p=332#comment-4537</guid>
		<description>Thanks,

At the same time suPHP may make individual accounts more vulnerably to attacks that use buggy scripts, since 644 and 755 permissions won&#039;t prevent file modification and creation. Am I right?

And it is still not clear if suPHP can prevent Beladen/Goscanpark attacks.</description>
		<content:encoded><![CDATA[<p>Thanks,</p>
<p>At the same time suPHP may make individual accounts more vulnerably to attacks that use buggy scripts, since 644 and 755 permissions won&#8217;t prevent file modification and creation. Am I right?</p>
<p>And it is still not clear if suPHP can prevent Beladen/Goscanpark attacks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MK</title>
		<link>http://blog.unmaskparasites.com/2009/10/04/tweet-week-sept-28-oct-4-2009/comment-page-1/#comment-4535</link>
		<dc:creator>MK</dc:creator>
		<pubDate>Tue, 06 Oct 2009 05:28:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.unmaskparasites.com/?p=332#comment-4535</guid>
		<description>suPHP, in combination with other precautions, is a very good method of protection against attacks aimed at the server itself. PHP processes are run as individual users rather than &quot;nobody&quot; or something similar. This allows much more restrictive permissions to be setup and in doing so, prevents a compromise of one account to spread to multiple accounts or the server itself.</description>
		<content:encoded><![CDATA[<p>suPHP, in combination with other precautions, is a very good method of protection against attacks aimed at the server itself. PHP processes are run as individual users rather than &#8220;nobody&#8221; or something similar. This allows much more restrictive permissions to be setup and in doing so, prevents a compromise of one account to spread to multiple accounts or the server itself.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
