Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DoS attack possible #13

Closed
GoogleCodeExporter opened this issue Mar 17, 2015 · 3 comments
Closed

DoS attack possible #13

GoogleCodeExporter opened this issue Mar 17, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

It is highly demanded, to implement an dos(denial of service) blocker.

The easiest way should be, to ask about a simple key file
 like "http://example.com/skipfish_[sha_digest_hex].html"


Original issue reported on code.google.com by res...@googlemail.com on 21 Mar 2010 at 5:05

@GoogleCodeExporter
Copy link
Author

Firstly, the project is open source; nothing would prevent a malicious party 
from 
simply removing this check.

Secondly, using a scanner with the intent to launch a denial-of-service attack 
is an 
odd move. There are far more efficient and simpler tools you can use if your 
only goal 
is to overload the server (even Apache benchmarking tool is probably more 
dangerous).

Original comment by lcam...@gmail.com on 21 Mar 2010 at 5:35

  • Changed state: Invalid

@GoogleCodeExporter
Copy link
Author

What about some decent defaults to -m -g -d -c -r parameter?


Original comment by res...@googlemail.com on 21 Mar 2010 at 6:11

@GoogleCodeExporter
Copy link
Author

What's not decent about the defaults, specifically? -m is capped at 10, which 
seems 
rather sensible (with keep-alive hosts in particular). You also can't run the 
scanner 
until you actually look at the documentation and jump through some hops 
(picking a 
dictionary, specifying -o).

DoS defenses should really be implemented on server side; and if this tool is 
causing 
you trouble, you probably have a significant problem anyway.

Original comment by lcam...@gmail.com on 21 Mar 2010 at 8:45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant