bugtraq - Re: a cheesy Apache / IIS DoS vuln (+a question)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 04 Jan 2007 02:34:14 -0600
From: "William A. Rowe, Jr." <wrowe@...e-clan.net>
To: Michal Zalewski <lcamtuf@...ne.ids.pl>
Cc: bugtraq@...urityfocus.com, full-disclosure@...sys.com
Subject: Re: a cheesy Apache / IIS DoS vuln (+a question)

Michal Zalewski wrote:
> On Wed, 3 Jan 2007, William A. Rowe, Jr. wrote:
> 
>> If you have an issue with this behavior, of HTTP, then you have an issue
>> with the behavior under FTP or a host of other protocols.
> 
> Not really; see above. These are typically well known, preventable by
> configuring server-side limits, and require a much higher overhead.

On the matter of your 1GB window (which is, again, the real issue), you have
any examples of a kernel that permits that large a sliding window buffer by
default, or any examples where this is commonly set quite that high?  If
not, what is your logic for negotiating a packet window larger than the OS
will permit?