Description: This is part 3 of a 6 part series showing you the method to the madness behind Armitage for Metasploit. This lecture teaches you how to use Metasploit to break into hosts. You'll learn how to hack without exploits, use client-side attacks, and launch the right remote exploit when applicable. Complete series is at http://www.ethicalhacker.net/content/view/379/1/
Tags: metasploit , armitage , client-side attacks , remote exploits , trojans ,
Disclaimer: We are a infosec video aggregator and this video is linked from an external website. The original author may be different from the user re-posting/linking it here. Please do not assume the authors to be same without verifying.
Very informative,, thanks!!!
Great...
Anyone have a good link how to setup postgresql server on backtrack 5! I am stuck there and...can't test without database running ...
Thanks in advance!
I believe it's automated now isn't it?
run msfconsole -> db_driver postgresql -> db_status
If it says connected, then you are good to go. Otherwise:
db_connect
Also make sure you run msfupdate beforehand to get the latest version
@Sulimanw all of these videos show Armitage running on a clean BT5 instance with an msfupdate to 4.0. If you click Start MSF, everything will work like you'd expect. There is no need to change the database settings or start the postgresql server by hand. -- Be sure to read the documentation first, it will help you avoid pitfalls. http://www.fastandeasyhacking.com/manual
This is one of the best Armitage tutorials I found!! But I got a question for you. I know that 192.168.x.x is a private IP address. How can I use Armitage or Metasploit with remote WAN IP address?
Thanks all,
It works well...
thanks again for a perfect tutorial.
Thanks Sir..
i am really enjoying the comfort of Armitage.. :)
Sorry, im really new to, well everything. I just found out about metasploit and backtrack 2 days ago. When you did the quick scan (OS) and put an IP adress in, what IP was that? I tried this tutorial on a Vurtual machine (windows XP) and got the IP from command prompt>ipconfig, but later when I tried ANY of the exploits it said LOGON_ACCESS_FAILURE.
Sorry, that last error message was supposed to be STATUS_LOGON_FAILURE