<?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: jQuery.com DOS Attacks</title>
	<atom:link href="http://ajaxian.com/archives/jquerycom-dos-attacks/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/jquerycom-dos-attacks</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 09 Feb 2012 06:55:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: Vlad</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-257531</link>
		<dc:creator>Vlad</dc:creator>
		<pubDate>Mon, 22 Oct 2007 16:00:46 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-257531</guid>
		<description>from http://tools.ietf.org/html/rfc4732
Eliminate Bad Traffic Early
   Many DoS attacks are generic bandwidth consumption attacks that
   operate by clogging the link that connects the victim server to the
   Internet.  Filtering these attacks at the server does no good because
   the traffic has already traversed the link that is the scarce
   resource.  Such flows need to be filtered at some point closer to the
   attacker.  Where possible, operators should filter out obviously bad
   traffic.  In particular, they should perform ingress filtering.</description>
		<content:encoded><![CDATA[<p>from <a href="http://tools.ietf.org/html/rfc4732" rel="nofollow">http://tools.ietf.org/html/rfc4732</a><br />
Eliminate Bad Traffic Early<br />
   Many DoS attacks are generic bandwidth consumption attacks that<br />
   operate by clogging the link that connects the victim server to the<br />
   Internet.  Filtering these attacks at the server does no good because<br />
   the traffic has already traversed the link that is the scarce<br />
   resource.  Such flows need to be filtered at some point closer to the<br />
   attacker.  Where possible, operators should filter out obviously bad<br />
   traffic.  In particular, they should perform ingress filtering.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250452</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Mon, 14 May 2007 19:05:17 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250452</guid>
		<description>Thank you for clarifying, John. It was just frustrating learning of this &quot;article&quot; where the hosting company was made to sound complacent and uninterested in helping the customer, when that is the complete opposite of what actually took place. Yes it was a big inconvenience for you guys to have to have moved your site. It was also an inconvenience for other customers that had to suffer because someone else on the server was getting repeatedly attacked. Due to the lack of a single complaint from any other customer on the server, I&#039;d say we handled it as quickly and efficiently as possible, both times. It would have been negligent of us to not take immediate action in an effort to maintain server stability. 

It&#039;s an undesirable situation for everyone involved - you, the other customers, and us. In the end a business decision had to be made for the benefit and stability of our customers and our server. No hard feelings, nothing personal, just trying to maintain the high quality of service that we have always provided, and will continue to provide. 

Anyone wanting to &quot;warn&quot; someone else about us should know that best efforts are made to assist every customer, even for an unmanaged service such as the VDS offerings.

I agree with putting this issue to rest. Best of luck to you all, and congratulations on your success. I am proud to be part of the company that hosted jquery.com on a server that had uptimes as long as 277 days without a single issue, requiring a reboot only for proactively installing a new kernel to address security updates (this is documented in our forums). Take care.</description>
		<content:encoded><![CDATA[<p>Thank you for clarifying, John. It was just frustrating learning of this &#8220;article&#8221; where the hosting company was made to sound complacent and uninterested in helping the customer, when that is the complete opposite of what actually took place. Yes it was a big inconvenience for you guys to have to have moved your site. It was also an inconvenience for other customers that had to suffer because someone else on the server was getting repeatedly attacked. Due to the lack of a single complaint from any other customer on the server, I&#8217;d say we handled it as quickly and efficiently as possible, both times. It would have been negligent of us to not take immediate action in an effort to maintain server stability. </p>
<p>It&#8217;s an undesirable situation for everyone involved &#8211; you, the other customers, and us. In the end a business decision had to be made for the benefit and stability of our customers and our server. No hard feelings, nothing personal, just trying to maintain the high quality of service that we have always provided, and will continue to provide. </p>
<p>Anyone wanting to &#8220;warn&#8221; someone else about us should know that best efforts are made to assist every customer, even for an unmanaged service such as the VDS offerings.</p>
<p>I agree with putting this issue to rest. Best of luck to you all, and congratulations on your success. I am proud to be part of the company that hosted jquery.com on a server that had uptimes as long as 277 days without a single issue, requiring a reboot only for proactively installing a new kernel to address security updates (this is documented in our forums). Take care.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250451</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Mon, 14 May 2007 18:34:50 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250451</guid>
		<description>I&#039;d also ask everyone to not immediately assume the hosting provider is at fault.  We go to great lengths to help each and every customer.  In this case our hands were tied.

@ Rey &quot;and running during our previous hostâ€™s less than business-like termination of the hosting service&quot;  

its comments like the above which are unfounded and unnecessary.</description>
		<content:encoded><![CDATA[<p>I&#8217;d also ask everyone to not immediately assume the hosting provider is at fault.  We go to great lengths to help each and every customer.  In this case our hands were tied.</p>
<p>@ Rey &#8220;and running during our previous hostâ€™s less than business-like termination of the hosting service&#8221;  </p>
<p>its comments like the above which are unfounded and unnecessary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rey Bango</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250450</link>
		<dc:creator>Rey Bango</dc:creator>
		<pubDate>Mon, 14 May 2007 18:01:23 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250450</guid>
		<description>@John: Ah okay. I&#039;m glad that they gave you access to get the data off.

@Jeff: John has clarified what you meant by shared hosting and also the immediacy of your decisions.

Hopefully, this issue can be put to rest as there&#039;s lots to be done with the jQuery library.</description>
		<content:encoded><![CDATA[<p>@John: Ah okay. I&#8217;m glad that they gave you access to get the data off.</p>
<p>@Jeff: John has clarified what you meant by shared hosting and also the immediacy of your decisions.</p>
<p>Hopefully, this issue can be put to rest as there&#8217;s lots to be done with the jQuery library.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Resig</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250449</link>
		<dc:creator>John Resig</dc:creator>
		<pubDate>Mon, 14 May 2007 17:51:38 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250449</guid>
		<description>@Rey - for all technical purposes, a VDS is a &quot;shared&quot; hosting solution (multiple environments within a single machine). That&#039;s what Jeff was referring to.

Unfortunately, in a situation like this it&#039;s not always possible to provide &quot;due notice&quot; - since the attacks were occurring immediately. They did give me continued access to the server, to move information off - but since the direction of the attacks was undetermined, they had to shut down all, possibly-breached, services (such as the web server).</description>
		<content:encoded><![CDATA[<p>@Rey &#8211; for all technical purposes, a VDS is a &#8220;shared&#8221; hosting solution (multiple environments within a single machine). That&#8217;s what Jeff was referring to.</p>
<p>Unfortunately, in a situation like this it&#8217;s not always possible to provide &#8220;due notice&#8221; &#8211; since the attacks were occurring immediately. They did give me continued access to the server, to move information off &#8211; but since the direction of the attacks was undetermined, they had to shut down all, possibly-breached, services (such as the web server).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rey Bango</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250448</link>
		<dc:creator>Rey Bango</dc:creator>
		<pubDate>Mon, 14 May 2007 17:23:08 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250448</guid>
		<description>@Jeff: First to be clear, I&#039;m not the account holder of the server. John is. 

Next, I don&#039;t consider a VDS to be shared hosting solution and from your website, neither do you. To quote from your own marketing material:

&quot;A virtual dedicated server (VDS) acts like a dedicated server in every way â€“ while retaining the ease-of-use of virtual hosting. VDS costs far less than dedicated, but you get root access, your own mail server, your own IP number, and a lot more. It&#039;s the choice for serious developers, ecommerce sites, or any other Web business that&#039;s outgrown its shared hosting environment.&quot;

The last sentence is a complete contradiction to your statement.

Finally, nobody on the jQuery team has either mentioned your company name nor publicly lambasted you. If anything, all of us have avoided mentioning the issue and focused on thanking folks for their support. What others not associated with the project find via their own initiative is their prerogative.

Irregardless of the circumstances, you shut down the jQuery site with no notice and shut out a number of people that are dependent on this open source project for their day to day work. If you had given John ample notice that the site needed to be moved, especially considering the past issues that you mentioned, I&#039;m sure that he would&#039;ve obliged, moved the site and helped alleviate your immediate concerns.</description>
		<content:encoded><![CDATA[<p>@Jeff: First to be clear, I&#8217;m not the account holder of the server. John is. </p>
<p>Next, I don&#8217;t consider a VDS to be shared hosting solution and from your website, neither do you. To quote from your own marketing material:</p>
<p>&#8220;A virtual dedicated server (VDS) acts like a dedicated server in every way â€“ while retaining the ease-of-use of virtual hosting. VDS costs far less than dedicated, but you get root access, your own mail server, your own IP number, and a lot more. It&#8217;s the choice for serious developers, ecommerce sites, or any other Web business that&#8217;s outgrown its shared hosting environment.&#8221;</p>
<p>The last sentence is a complete contradiction to your statement.</p>
<p>Finally, nobody on the jQuery team has either mentioned your company name nor publicly lambasted you. If anything, all of us have avoided mentioning the issue and focused on thanking folks for their support. What others not associated with the project find via their own initiative is their prerogative.</p>
<p>Irregardless of the circumstances, you shut down the jQuery site with no notice and shut out a number of people that are dependent on this open source project for their day to day work. If you had given John ample notice that the site needed to be moved, especially considering the past issues that you mentioned, I&#8217;m sure that he would&#8217;ve obliged, moved the site and helped alleviate your immediate concerns.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250442</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Mon, 14 May 2007 16:33:02 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250442</guid>
		<description>One other thing I&#039;ll add:

===
@Nice: We werenâ€™t on a shared server.
Comment by Rey Bango â€” May 8, 2007
===

Yes, you were on a shared server. Oblivious to the server being hacked repeatedly for days at a time, oblivious about the service you had.</description>
		<content:encoded><![CDATA[<p>One other thing I&#8217;ll add:</p>
<p>===<br />
@Nice: We werenâ€™t on a shared server.<br />
Comment by Rey Bango â€” May 8, 2007<br />
===</p>
<p>Yes, you were on a shared server. Oblivious to the server being hacked repeatedly for days at a time, oblivious about the service you had.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250440</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Mon, 14 May 2007 16:14:56 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250440</guid>
		<description>Not only can the web bring out the worst in people, it can also bring out misinformation (who&#039;da thunk it?!)

The author of this article is apparently not a big fan of fact checking. The fact is that the customer&#039;s server was hacked twice, and the attacks that occurred as a result affected all customers on the server for a brief period of time in both cases. Efforts were made to protect all customers on the server, including the server hosting jquery.com. Assistance was offered by the hosting company to determine the method of attack after the first attack. No response was given to the hosting company from the customer in regards to the aforementioned offering of assistance.

If a customer fails to maintain control over their server multiple times, resulting in attacks that can negatively affect performance of all customers on the server, then that customer will be asked to leave. One customer&#039;s website and needs do not trump the needs of the customer base on the server as a whole. 

The customer in this case was not shut off by the hosting company, immediate actions were taken in both cases to protect everyone on the server, and the customer was informed that he could keep his hosting services with us, but that the attacked site would need to find a new host.

If you are going to assume the role of a Linux system&#039;s administrator, then you must do your duty to be one. It is not the hosting company&#039;s fault that the customer&#039;s server was hacked and DDoSd (not DoSd), nor is it the hosting company&#039;s fault that the local system&#039;s administrator (customer) failed to investigate the issue to patch the hole, resulting in the second attack which prompted the hosting company to inform the customer that the site would need to find a new home. Nice try shifting the blame on the hosting company with lies and misinfomation though.</description>
		<content:encoded><![CDATA[<p>Not only can the web bring out the worst in people, it can also bring out misinformation (who&#8217;da thunk it?!)</p>
<p>The author of this article is apparently not a big fan of fact checking. The fact is that the customer&#8217;s server was hacked twice, and the attacks that occurred as a result affected all customers on the server for a brief period of time in both cases. Efforts were made to protect all customers on the server, including the server hosting jquery.com. Assistance was offered by the hosting company to determine the method of attack after the first attack. No response was given to the hosting company from the customer in regards to the aforementioned offering of assistance.</p>
<p>If a customer fails to maintain control over their server multiple times, resulting in attacks that can negatively affect performance of all customers on the server, then that customer will be asked to leave. One customer&#8217;s website and needs do not trump the needs of the customer base on the server as a whole. </p>
<p>The customer in this case was not shut off by the hosting company, immediate actions were taken in both cases to protect everyone on the server, and the customer was informed that he could keep his hosting services with us, but that the attacked site would need to find a new host.</p>
<p>If you are going to assume the role of a Linux system&#8217;s administrator, then you must do your duty to be one. It is not the hosting company&#8217;s fault that the customer&#8217;s server was hacked and DDoSd (not DoSd), nor is it the hosting company&#8217;s fault that the local system&#8217;s administrator (customer) failed to investigate the issue to patch the hole, resulting in the second attack which prompted the hosting company to inform the customer that the site would need to find a new home. Nice try shifting the blame on the hosting company with lies and misinfomation though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250438</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Mon, 14 May 2007 15:37:55 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250438</guid>
		<description>To set the record straight

&quot;our host didnâ€™t want to deal with the influx of traffic that was bombarding us, so they simply just kicked us out.&quot;

Is not a true statement.  John -- really, I expected better out of you.

A true statement would be:

&quot;My server was compromised not once but twice.  In both instances someone setup an IRC server on my server which was the target of a decent sized denial of service attack - 350Mbps+.&quot;   &quot;Additionally, since I was unable to determine how the attackers got in (twice), my host asked me to move this website elsewhere as to not further disrupt the service provided to other customers&quot;.</description>
		<content:encoded><![CDATA[<p>To set the record straight</p>
<p>&#8220;our host didnâ€™t want to deal with the influx of traffic that was bombarding us, so they simply just kicked us out.&#8221;</p>
<p>Is not a true statement.  John &#8212; really, I expected better out of you.</p>
<p>A true statement would be:</p>
<p>&#8220;My server was compromised not once but twice.  In both instances someone setup an IRC server on my server which was the target of a decent sized denial of service attack &#8211; 350Mbps+.&#8221;   &#8220;Additionally, since I was unable to determine how the attackers got in (twice), my host asked me to move this website elsewhere as to not further disrupt the service provided to other customers&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rey Bango</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250323</link>
		<dc:creator>Rey Bango</dc:creator>
		<pubDate>Wed, 09 May 2007 17:20:44 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250323</guid>
		<description>@Marc: Thank you for the donation! :)

To all of the project supporters, thank you so much for your words of encouragement and continued support. Whether its jQuery, Prototype, Audacity, Gaim or any open source effort, its a shame that some people will do these things just for the sake of doing it.

Thanks again.</description>
		<content:encoded><![CDATA[<p>@Marc: Thank you for the donation! :)</p>
<p>To all of the project supporters, thank you so much for your words of encouragement and continued support. Whether its jQuery, Prototype, Audacity, Gaim or any open source effort, its a shame that some people will do these things just for the sake of doing it.</p>
<p>Thanks again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250312</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Wed, 09 May 2007 15:28:10 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250312</guid>
		<description>&quot;John and the rest of the jQuery team are not likely to reveal the previous hosting provider. (Libel lawsuits, anyone?)&quot;

I know the UK has easy libel laws, but in what country could revealing their previous provider be construed as libel?</description>
		<content:encoded><![CDATA[<p>&#8220;John and the rest of the jQuery team are not likely to reveal the previous hosting provider. (Libel lawsuits, anyone?)&#8221;</p>
<p>I know the UK has easy libel laws, but in what country could revealing their previous provider be construed as libel?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ANBe</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250281</link>
		<dc:creator>ANBe</dc:creator>
		<pubDate>Tue, 08 May 2007 17:27:07 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250281</guid>
		<description>Dos attack to JQuery -&gt; despicable behaviour
Host company -&gt; I think that they aren&#039;t real professionals.  The solution they provide to this problem was the easiest way.  Anyone can do it.</description>
		<content:encoded><![CDATA[<p>Dos attack to JQuery -&gt; despicable behaviour<br />
Host company -&gt; I think that they aren&#8217;t real professionals.  The solution they provide to this problem was the easiest way.  Anyone can do it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Grabanski</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250278</link>
		<dc:creator>Marc Grabanski</dc:creator>
		<pubDate>Tue, 08 May 2007 16:04:28 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250278</guid>
		<description>&quot;Quick, they are giving away free stuff and helping the community.. lets take them down!&quot; -DOS Attackers

I donated. Go jQuery!</description>
		<content:encoded><![CDATA[<p>&#8220;Quick, they are giving away free stuff and helping the community.. lets take them down!&#8221; -DOS Attackers</p>
<p>I donated. Go jQuery!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nthalk</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250272</link>
		<dc:creator>Nthalk</dc:creator>
		<pubDate>Tue, 08 May 2007 15:13:12 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250272</guid>
		<description>Tim, you appear to be right.

jQuery.com&#039;s recorded IP in 2005-12-12 shows the following whois netblock:
http://whois.domaintools.com/209.8.234.21

CustName:  SecurityMinded Technologies LLC. Dba Myriad Network
Address:  37 Pidgeon Hill Drive
Address:  #106
City:    Sterling
StateProv: VA
PostalCode: 20165
Country:  US 

My employer kicks ass for figuring out this sort of stuff.</description>
		<content:encoded><![CDATA[<p>Tim, you appear to be right.</p>
<p>jQuery.com&#8217;s recorded IP in 2005-12-12 shows the following whois netblock:<br />
<a href="http://whois.domaintools.com/209.8.234.21" rel="nofollow">http://whois.domaintools.com/209.8.234.21</a></p>
<p>CustName:  SecurityMinded Technologies LLC. Dba Myriad Network<br />
Address:  37 Pidgeon Hill Drive<br />
Address:  #106<br />
City:    Sterling<br />
StateProv: VA<br />
PostalCode: 20165<br />
Country:  US </p>
<p>My employer kicks ass for figuring out this sort of stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rey Bango</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250264</link>
		<dc:creator>Rey Bango</dc:creator>
		<pubDate>Tue, 08 May 2007 13:41:03 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250264</guid>
		<description>@Nice: We weren&#039;t on a shared server.</description>
		<content:encoded><![CDATA[<p>@Nice: We weren&#8217;t on a shared server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nice</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250249</link>
		<dc:creator>Nice</dc:creator>
		<pubDate>Tue, 08 May 2007 08:32:08 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250249</guid>
		<description>It doesn&#039;t matter who that host was because *every* shared host out there is going to boot you off of a server if you&#039;re the target of an attack.  They can lose one customer to save a server of 100 customers, or lose 100 customers just to save one customer.  DOS scenarios are what you discuss when purchasing a dedicated or colo server, not at some $9.99 cattleherding host.</description>
		<content:encoded><![CDATA[<p>It doesn&#8217;t matter who that host was because *every* shared host out there is going to boot you off of a server if you&#8217;re the target of an attack.  They can lose one customer to save a server of 100 customers, or lose 100 customers just to save one customer.  DOS scenarios are what you discuss when purchasing a dedicated or colo server, not at some $9.99 cattleherding host.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TaL</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250247</link>
		<dc:creator>TaL</dc:creator>
		<pubDate>Tue, 08 May 2007 07:42:14 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250247</guid>
		<description>Was the old hosting company &quot;SecurityMinded Technologies LLC&quot;??</description>
		<content:encoded><![CDATA[<p>Was the old hosting company &#8220;SecurityMinded Technologies LLC&#8221;??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Cooijmans</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250246</link>
		<dc:creator>Tim Cooijmans</dc:creator>
		<pubDate>Tue, 08 May 2007 07:09:35 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250246</guid>
		<description>It&#039;s not libel if it&#039;s true.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not libel if it&#8217;s true.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: s</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250244</link>
		<dc:creator>s</dc:creator>
		<pubDate>Tue, 08 May 2007 03:31:10 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250244</guid>
		<description>why should one attack a community site?, 
recently javarss.com was also hacked...


sudhir
http://www.jyog.com</description>
		<content:encoded><![CDATA[<p>why should one attack a community site?,<br />
recently javarss.com was also hacked&#8230;</p>
<p>sudhir<br />
<a href="http://www.jyog.com" rel="nofollow">http://www.jyog.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Geary</title>
		<link>http://ajaxian.com/archives/jquerycom-dos-attacks/comment-page-1#comment-250243</link>
		<dc:creator>Michael Geary</dc:creator>
		<pubDate>Tue, 08 May 2007 03:20:16 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/archives/jquerycom-dos-attacks#comment-250243</guid>
		<description>John and the rest of the jQuery team are not likely to reveal the previous hosting provider. (Libel lawsuits, anyone?)

Nonetheless, I am as curious as anyone else to know who they are! They certainly deserve a black eye. [sigh]</description>
		<content:encoded><![CDATA[<p>John and the rest of the jQuery team are not likely to reveal the previous hosting provider. (Libel lawsuits, anyone?)</p>
<p>Nonetheless, I am as curious as anyone else to know who they are! They certainly deserve a black eye. [sigh]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

