full-disclosure - Goolag Perk and Annoyance

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-next>] [day] [month] [year] [list]

Message-ID: <47CEB241.3020604@krr.org>
Date: Wed, 05 Mar 2008 07:46:25 -0700
From: Times Enemy <times@....org>
To: full-disclosure@...ts.grok.org.uk
Subject: Goolag Perk and Annoyance

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings.

I preface that this is not a discovery, but rather a simple observation.

http://www.goolag.org

I am finding that it takes only a few seconds for Google to block query
requests, BY IP!  With this in mind, Goolag Scanner is actually an
effective annoyance tool against large networks.  Simply conduct a
Goolag Scan from a heavily populated network, with a couple hundred
Dorks, and anyone who uses the same public IP address which was used for
the Goolag Scan will have to go through an extra CAPTCHA step to finish
their Google queries.  If they use a Google toolbar of some sort, Google
may not even offer them a CAPTCHA option to continue with the search query.

Within "most" corporate networks, what effective methods can be used,
from the network's perspective, to block mass Google queries?

.te
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkfOskEACgkQVuM8PD1Unspb8QCbBLYgUYKvp7CxnlA3RhLo5ec9
+wAAn35WpzMIvnyaLT4qmho/0O8QbtNN
=bYe4
-----END PGP SIGNATURE-----

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