Penetration Testing mailing list archives

Re: Google getting smarter ?!?!


From: stonersavant <dank.krew () gmail com>
Date: Fri, 4 Feb 2005 06:33:34 -0800

I hate to be contrary, but isn't it more likely that it is filtering
out requests for php based not on a tool limited to the Google API
which cuts you off after 1000 searches, but rather based on queries
that are utilized by worms?

SiteDigger 2.0 has been out a while now, and it's not effective enough
a tool to be utilized by script kiddies as a mass penetration device
since the queries are used in context of a specific site. You won't
find any results with an automated google hacking maching that you
wouldn't by typing site:somesite.com anyway. Besides, with the GHDB
now topping out at over 1,000 entries you can't do a complete scan.

Google hacking isn't dead, it's just evolving.

$.02 - stoner.savant, http://johnny.ihackstuff.com/

On Thu, 3 Feb 2005 10:59:59 +0000, William Allsopp
<William_Allsopp () eur 3com com> wrote:


John,

This is almost certainly in response to the recent release of Foundstone's
script kiddie tool du jour: Sitedigger 2.0, which would likely have increased
this kind of traffic a hundred fold. Google is 'getting smarter' but not to a
great degree. For example, you are correct that a search on admin.php will flag,
but you can still manipulate the search to get around that. Experiment. However,
this is probably the beginning of the end for google hacking and we can expect
to see considerably more search filtering being put in place.

Regards,

WA

----------------------------------------------------

Hi,

I noticed today that a simple search in Google using
inurl causes Google to display this message when you
try to access the second page:

===================================================

We're sorry...
... but we can't process your request right now. A
computer virus or spyware application is sending us
automated requests, and it appears that your computer
or network has been

<snip>




-- 
someone is watching you.


Current thread: