
This brings us back, once again, to perhaps the most valuable weapon in a
Google hacker’s arsenal: effective search reduction. Here’s a list of the most
common points a Google hacker considers when trolling for configuration files:
■
Create a strong base search using unique words or phrases from live files.
■
Filter out the words sample, example, test, howto, and tutorial to narrow the
obvious example files.
■
Filter out CVS repositories, which often house default config files,
with –cvs.
■
Filter out manpage or Manual if you’re searching for a UNIX program’s
configuration file.
■
Locate the one most commonly changed field in a sample configuration
file and perform a ...