full-disclosure - Re: how to detect DDoS attack through HTTP response analysis(throuput)

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: Wed, 29 Jun 2011 09:40:05 +0200
From: Ferenc Kovacs <tyra3l@...il.com>
To: coderman <coderman@...il.com>
Cc: full-disclosure@...ts.grok.org.uk, pen-test@...urityfocus.com
Subject: Re: how to detect DDoS attack through HTTP
	response analysis(throuput)

2011/6/29 coderman <coderman@...il.com>:
> 2011/6/26 김무성 <kimms@...osec.co.kr>:
>> ...
>> I'm looking for meterials or information, research about that how to detect
>> DDoS attack through HTTP response analysis(throuput).
>
> you're asking the wrong question.
>
> instead of asking "How can I automagically detect exploitation of my
> shitty app via HTTP Resp. codes"
>
> ask: "Why is my webapp so shitty that any number of arbitrary requests
> lead to resource exhaustion?"
>

because fetching(or imitating to fetch) the result is always less
resource intense than generating it?
o_O

Tyrael

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/