<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Myspace&#x27;s problem in </title>
<link>http://www.dslreports.com/forum/r17252828</link>
<description></description>
<language>en</language>
<pubDate>Wed, 02 Dec 2009 23:53:23 EDT</pubDate>
<lastBuildDate>Wed, 02 Dec 2009 23:53:23 EDT</lastBuildDate>

<item>
<title>Re: Myspace&#x27;s problem</title>
<link>http://www.dslreports.com/forum/remark,17254287</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I have to disagree.  Yes, MySpace bears some responsibility, but the hosting provider where the phished information ends up has a responsibility to act when they are advised of what's going on.<br><br>A close but not perfect analogy would be if stolen goods were showing up in a pawn shop.  Even if the pawn shop owner really didn't know the items were stolen when the thief began pawning them, as soon as he's shown that they are indeed stolen, he can not plead ignorance or maintain that he has no responsibility to do anything to assist in catching the thief.<br><br>To return to the MySpace situation, the Web hosting company owners also need to realize that, if this incident prompts a criminal investigation, they could be charged with aiding and abetting the perpetrators of the crime.  It's one thing if they didn't know what was going on, but as soon as they're told, they can't just ignore what's happening.  If they're smart, they'd better be preserving as much evidence as they can and contacting an attorney because if this does get investigated, they're the first people the police will come to.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,17254287</guid>
<pubDate>Fri, 10 Nov 2006 21:38:21 EDT</pubDate>
</item>

<item>
<title>Re: Myspace&#x27;s problem</title>
<link>http://www.dslreports.com/forum/remark,17252974</link>
<description><![CDATA[<A HREF="/useremail/u/268987"><b>Sebastian</b></A> : no one is at fault except for myspace.. clearly they should keep an eye on what the hell people are embedding into the pages they create.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,17252974</guid>
<pubDate>Fri, 10 Nov 2006 16:26:21 EDT</pubDate>
</item>

<item>
<title>Re: Myspace&#x27;s problem</title>
<link>http://www.dslreports.com/forum/remark,17252954</link>
<description><![CDATA[<A HREF="/useremail/u/485965"><b>buzzcut</b></A> : I don't think anybody blames the hosting provider for somebody else's security problem, but when they are found to be abetting in that activity, aren't there any good-citizen obligations to help mitigate the damage?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,17252954</guid>
<pubDate>Fri, 10 Nov 2006 16:23:29 EDT</pubDate>
</item>

<item>
<title>Myspace&#x27;s problem</title>
<link>http://www.dslreports.com/forum/remark,17252828</link>
<description><![CDATA[<A HREF="/useremail/u/695790"><b>texans20</b></A> : Myspace has not done enough to protect the security of their own network or site. Spam is rampant, and phishing has always been a problem. Some changes to what is allowed on a profile should be the first step. Removing php or any other script from being allowed to sit on a profile should be the first step.<br><br>It's not the hosting providor's fault myspace is lacking in some security. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,17252828</guid>
<pubDate>Fri, 10 Nov 2006 16:02:05 EDT</pubDate>
</item>

</channel>
</rss>
