Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 24981 invoked from network); 7 Oct 2009 00:08:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Oct 2009 00:08:05 -0000 Received: (qmail 87443 invoked by uid 500); 7 Oct 2009 00:08:04 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 87360 invoked by uid 500); 7 Oct 2009 00:08:04 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 87351 invoked by uid 99); 7 Oct 2009 00:08:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Oct 2009 00:08:04 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [64.202.165.95] (HELO smtpauth04.prod.mesa1.secureserver.net) (64.202.165.95) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 07 Oct 2009 00:07:53 +0000 Received: (qmail 28076 invoked from network); 7 Oct 2009 00:07:31 -0000 Received: from unknown (76.252.112.72) by smtpauth04.prod.mesa1.secureserver.net (64.202.165.95) with ESMTP; 07 Oct 2009 00:07:31 -0000 Message-ID: <4ACBDBB2.70700@rowe-clan.net> Date: Tue, 06 Oct 2009 19:07:14 -0500 From: "William A. Rowe, Jr." User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: "dev@httpd.apache.org" Subject: A proposed DDoS solution X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org http://www.scientificcomputing.com/news-HPC-Denial-of-Service-Denied-100209.aspx Might be of interest to some of the developers here. Not entirely sure that it is realistic to solve this below layer 7 in the manner described, but it's certainly interesting to watch folks attempt to wrastle this problem, especially in light of our infra's recent confrontations of the issue.