msf > msfupdate
Updated to revision 13755
root@bt:~# msfconsole
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
MMMMMMMMMMM MMMMMMMMMM
MMMN$ vMMMM
MMMNl MMMMM MMMMM JMMMM
MMMNl MMMMMMMN NMMMMMMM JMMMM
MMMNl MMMMMMMMMNmmmNMMMMMMMMM JMMMM
MMMNI MMMMMMMMMMMMMMMMMMMMMMM jMMMM
MMMNI MMMMMMMMMMMMMMMMMMMMMMM jMMMM
MMMNI MMMMM MMMMMMM MMMMM jMMMM
MMMNI MMMMM MMMMMMM MMMMM jMMMM
MMMNI MMMNM MMMMMMM MMMMM jMMMM
MMMNI WMMMM MMMMMMM MMMM# JMMMM
MMMMR ?MMNM MMMMM .dMMMM
MMMMNm `?MMM MMMM` dMMMMM
MMMMMMN ?MM MM? NMMMMMN
MMMMMMMMNe JMMMMMNMMM
MMMMMMMMMMNm, eMMMMMNMMNMM
MMMMNNMNMMMMMNx MMMMMMNMMNMMNM
MMMMMMMMNMMNMMMMm+..+MMNMMNMNMMNMMNMM
=[ metasploit v4.0.1-dev [core:4.0 api:1.0]
+ -- --=[ 735 exploits - 376 auxiliary - 82 post
+ -- --=[ 228 payloads - 27 encoders - 8 nops
=[ svn r13755 updated today (2011.09.19)
root@bt:~# cd /opt/framework/msf3/
root@bt:/opt/framework/msf3# msfconsole
msf auxiliary(msfcrawler) > set THREADS 24
THREADS => 24
msf auxiliary(msfcrawler) > set RPORT 80
RPORT => 80
msf auxiliary(msfcrawler) > set PATH /
PATH => /
msf auxiliary(msfcrawler) > run
etc. armitage works perfectly. i do share similar concern/issue about postgresql.


