<?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 for Cybercrime Law</title>
	<atom:link href="http://www.cybercrimelaw.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cybercrimelaw.org</link>
	<description>News and analysis on cybercrime, information security and information privacy legal and technological issues.</description>
	<pubDate>Fri, 18 May 2012 03:44:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on &#8220;Open Wireless&#8221; Defense Not So Successful by Thomas</title>
		<link>http://www.cybercrimelaw.org/2007/10/05/open-wireless-defense-not-so-successful/comment-page-1/#comment-1016</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Sat, 18 Oct 2008 04:06:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.cybercrimelaw.org/2007/10/05/open-wireless-defense-not-so-successful/#comment-1016</guid>
		<description>So if we are responsible for what is on our network, who is responsible when a virus gets out? As the virus spreads across an ISP's network, should they be held liable? Since there are virtually millions of unsecure wireless networks, i can do anything illegal on someone else's network and they are punished???</description>
		<content:encoded><![CDATA[<p>So if we are responsible for what is on our network, who is responsible when a virus gets out? As the virus spreads across an ISP&#8217;s network, should they be held liable? Since there are virtually millions of unsecure wireless networks, i can do anything illegal on someone else&#8217;s network and they are punished???</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Reasonable Expectation of Privacy in Email Upheld by Republishing Email: The Great Debate - PlagiarismToday</title>
		<link>http://www.cybercrimelaw.org/2007/06/20/reasonable-expectation-of-privacy-in-email-upheld/comment-page-1/#comment-1009</link>
		<dc:creator>Republishing Email: The Great Debate - PlagiarismToday</dc:creator>
		<pubDate>Thu, 02 Oct 2008 16:48:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.cybercrimelaw.org/2007/06/20/reasonable-expectation-of-privacy-in-email-upheld/#comment-1009</guid>
		<description>[...] even though you may feel that there is no &#8220;reasonable expectation of privacy&#8221;, the courts seem to disagree. This is why the government needs a warrant to access your [...]</description>
		<content:encoded><![CDATA[<p>[...] even though you may feel that there is no &#8220;reasonable expectation of privacy&#8221;, the courts seem to disagree. This is why the government needs a warrant to access your [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Virginia Supreme Court Strikes Down State&#8217;s Anti-Spam Law by Leo</title>
		<link>http://www.cybercrimelaw.org/2008/09/12/virginia-supreme-court-strikes-down-states-anti-spam-law/comment-page-1/#comment-1008</link>
		<dc:creator>Leo</dc:creator>
		<pubDate>Wed, 24 Sep 2008 17:33:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.cybercrimelaw.org/2008/09/12/virginia-supreme-court-strikes-down-states-anti-spam-law/#comment-1008</guid>
		<description>There has also historically been a fairly sharp line drawn between speech and commercial speech, with more substantial limits being allowed on commercial speech.</description>
		<content:encoded><![CDATA[<p>There has also historically been a fairly sharp line drawn between speech and commercial speech, with more substantial limits being allowed on commercial speech.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Virginia Supreme Court Strikes Down State&#8217;s Anti-Spam Law by James Paulick</title>
		<link>http://www.cybercrimelaw.org/2008/09/12/virginia-supreme-court-strikes-down-states-anti-spam-law/comment-page-1/#comment-1004</link>
		<dc:creator>James Paulick</dc:creator>
		<pubDate>Sat, 13 Sep 2008 18:00:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.cybercrimelaw.org/2008/09/12/virginia-supreme-court-strikes-down-states-anti-spam-law/#comment-1004</guid>
		<description>I'll have to read the opinion, but this decision really surprises me.  There is an enormous difference between falsifying your ip address in order to effectuate bulk unsolicited mailings compared to publishing a political article anonymously.  

Surely the courts can distinguish the first amendment value of the latter compared to the evasiveness and worthlessness of the former.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll have to read the opinion, but this decision really surprises me.  There is an enormous difference between falsifying your ip address in order to effectuate bulk unsolicited mailings compared to publishing a political article anonymously.  </p>
<p>Surely the courts can distinguish the first amendment value of the latter compared to the evasiveness and worthlessness of the former.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on File Sharing Data Breach by Ymr</title>
		<link>http://www.cybercrimelaw.org/2008/07/09/file-sharing-data-breach/comment-page-1/#comment-987</link>
		<dc:creator>Ymr</dc:creator>
		<pubDate>Thu, 14 Aug 2008 06:33:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.cybercrimelaw.org/2008/07/09/file-sharing-data-breach/#comment-987</guid>
		<description>Cisco seems to say that writing a policy to block P2P sharing requires some proprietary skills or trade secrets. Some newer P2P packages (eg Limewire) were written to avoid using fixed ports so were designed to be hard to intercept.</description>
		<content:encoded><![CDATA[<p>Cisco seems to say that writing a policy to block P2P sharing requires some proprietary skills or trade secrets. Some newer P2P packages (eg Limewire) were written to avoid using fixed ports so were designed to be hard to intercept.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hacking for Investment Information by hailey</title>
		<link>http://www.cybercrimelaw.org/2007/04/08/hacking-for-investment-information/comment-page-1/#comment-968</link>
		<dc:creator>hailey</dc:creator>
		<pubDate>Mon, 19 May 2008 16:11:26 +0000</pubDate>
		<guid isPermaLink="false">#comment-968</guid>
		<description>i think this is a very nice site to search for cybercrime.
i love it!</description>
		<content:encoded><![CDATA[<p>i think this is a very nice site to search for cybercrime.<br />
i love it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Courts split on whether making a copyrighted song available for download violates copyright law. by Cybercrime Law &#187; No download, maybe no infringement in another Federal District Court</title>
		<link>http://www.cybercrimelaw.org/2008/04/27/courts-split-on-whether-making-a-copyrighted-song-available-for-download-violates-copyright-law/comment-page-1/#comment-967</link>
		<dc:creator>Cybercrime Law &#187; No download, maybe no infringement in another Federal District Court</dc:creator>
		<pubDate>Mon, 19 May 2008 12:50:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.cybercrimelaw.org/2008/04/27/courts-split-on-whether-making-a-copyrighted-song-available-for-download-violates-copyright-law/#comment-967</guid>
		<description>[...] Courts split on whether making a copyrighted song available for download violates copyright law. [...]</description>
		<content:encoded><![CDATA[<p>[...] Courts split on whether making a copyrighted song available for download violates copyright law. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What is your return address? by Raj</title>
		<link>http://www.cybercrimelaw.org/2008/03/27/what-is-your-return-address/comment-page-1/#comment-937</link>
		<dc:creator>Raj</dc:creator>
		<pubDate>Fri, 28 Mar 2008 07:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.cybercrimelaw.org/2008/03/27/what-is-your-return-address/#comment-937</guid>
		<description>Hi,

Very good article I think one should always
check e-mail before sending.

Thanks
Raj</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Very good article I think one should always<br />
check e-mail before sending.</p>
<p>Thanks<br />
Raj</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on When to change WEP to WPA? by Prabhat</title>
		<link>http://www.cybercrimelaw.org/2007/09/26/when-to-change-wep-to-wpa/comment-page-1/#comment-936</link>
		<dc:creator>Prabhat</dc:creator>
		<pubDate>Wed, 26 Mar 2008 12:12:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.cybercrimelaw.org/2007/09/26/when-to-change-wep-to-wpa/#comment-936</guid>
		<description>can you please tell whether it is a crime or not if a person, who knows the password of the other person's email account, deletes emails and chats without that person's knowledge and in the absence of that person? and can he/she be caught?</description>
		<content:encoded><![CDATA[<p>can you please tell whether it is a crime or not if a person, who knows the password of the other person&#8217;s email account, deletes emails and chats without that person&#8217;s knowledge and in the absence of that person? and can he/she be caught?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cost of insecurity by Cybercrime Law &#187; TXJ Costs Continue Increasing</title>
		<link>http://www.cybercrimelaw.org/2007/05/22/cost-of-insecurity/comment-page-1/#comment-871</link>
		<dc:creator>Cybercrime Law &#187; TXJ Costs Continue Increasing</dc:creator>
		<pubDate>Thu, 15 Nov 2007 16:41:27 +0000</pubDate>
		<guid isPermaLink="false">#comment-871</guid>
		<description>[...] wrote in May, under the title &#34;Cost of Insecurity&#34; about TJX Companies&#8217; costs in connection with the security breach suffered in [...]</description>
		<content:encoded><![CDATA[<p>[...] wrote in May, under the title &quot;Cost of Insecurity&quot; about TJX Companies&#8217; costs in connection with the security breach suffered in [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

