The Metasploit db_autopwn module
attempts to do this, adding in a database to keep track of the systems scanned by nmap
or Nessus. It is a clever concept, but the Metasploit 3.0 version of db_autopwn ends up
being more of a gimmick and not really super useful for professional pen-testers. It??™s a
fun toy, however, and makes for great security conference demos. Let??™s take a look at how
it works in BackTrack 2.0.
The first step is to get all the various parts and pieces required for db_autopwn. This
proved to be challenging on Windows under Cygwin. The good news is that BackTrack
2.0 includes everything you need. It even includes a script to perform the setup for you.
bt ~ # cd /pentest/exploits/framework3/
bt framework3 # ./start-db_autopwn
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.
The database cluster will be initialized with locale C.
creating directory /home/postgres/metasploit3 ... ok
creating directory /home/postgres/metasploit3/global ... ok
creating directory /home/postgres/metasploit3/pg_xlog ... ok
[??¦]
[**************************************************************]
[*] Postgres should be setup now. To run db_autopwn, please:
[*] # su - postgres
[*] # cd /pentest/exploits/framework3
{*] # .
Pages:
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267