Earlier quoted context omitted.
How could Google use hashes to avoid duplication? They'd have to download each link before they could hash the contents thereof, so the damage would still be done.
http://en.wikipedia.org/wiki/HTTP_ETag (I know that servers can be configured not to send ETags or break caches by sending random ones every time, but this could reduce the data usage considerably since most of the responses would only include the headers.)
A method to use Google for DDoS. Bug or Not?
31–40 of 54 posts
Re: A method to use Google for DDoS. Bug or Not?
#32Earlier quoted context omitted.
How could Google use hashes to avoid duplication? They'd have to download each link before they could hash the contents thereof, so the damage would still be done.
How could Google use hashes to avoid duplication? Rate limit per website (e.g. don't download more than 10 images per domain per second) Limit the total number of images it downloads per document, so a single user can not cause too much traffic.
Re: A method to use Google for DDoS. Bug or Not?
#33Re: A method to use Google for DDoS. Bug or Not?
#34Doesn't Facebook do something similar for preview links in chat and/or wall posts? You're probably limited by the number of messages/posts, but I wonder if that could be exploited with n number of fb accounts.
Re: A method to use Google for DDoS. Bug or Not?
#35This is about two years old: http://www.behind-the-enemy-lines.com/2012/04/google-attack-... I would hope that Google is able to detect abuse of their infrastructure for (D)DOS.
Indeed, I've quoted that article. But it doesn't talk about random parameters which makes it so easy to attack any website not just your own where you know what the urls are.
Re: A method to use Google for DDoS. Bug or Not?
#36Re: A method to use Google for DDoS. Bug or Not?
#37Re: A method to use Google for DDoS. Bug or Not?
#38Nice catch. I'm not so sure about: A simple fix will be just crawling the links without the request parameters so that we don’t have to suffer. Many links would fail/have different content if the request parameters were removed from the URL. Perhaps the crawler could use some kind of reverse bloom filter [1] to be more careful/back off if it receives the same content from multiple URLs. However nothing is simple at G…
=image("http://targetname/1.jpg")
=image("http://targetname/2.jpg")
=image("http://targetname/3.jpg")