search

Lubricy / armitage

Automatically exported from code.google.com/p/armitage
0 stars 0 forks source link

Teamserver Error: Unable to access jarfile Armitage.jar #152

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Use Kali 1.0.5
2. Starting the required services (PostgreSQL, metasploit), and use the 
msfconsole command to populate the database
3. Launch the Armitage Team Server (/usr/share/armitage/teamserver IP_ADDR 
PASSWORD 

What is the expected output? What do you see instead?

The credit for the fix goes to this YouTube author 
(http://www.youtube.com/watch?v=WxC3SZoErss), who shows the error and the fix.

What version of Metasploit are you using (type: svn info)? On which
operating system?
Metasploit stock version with Kali 1.0.5 (64-bit)

Which database are you using?

PostgreSQL

Please provide any additional information below.

The video above demonstrates the error and the fix.  By specifying the full 
path to armitage.jar in the teamserver file I'm unable to replicate the error.

Please let me know if you need more information.

Original issue reported on code.google.com by mmatc...@gmail.com on 10 Oct 2013 at 4:50

GoogleCodeExporter commented 9 years ago 
This is not an Armitage bug; but something I'd address with the Kali folks. 
Armitage's teamserver script assumes that the current working directory 
contains armitage.jar. The Kali package makes teamserver available globally. 
The script either needs to be changed for Kali (to hard code the path; or 
change to the armitage folder).

For now, cd to whereever armitage is installed and run teamserver from there.

Original comment by rsmu...@gmail.com on 10 Oct 2013 at 4:58

GoogleCodeExporter commented 9 years ago 
I didn't think it was a bug with Armitage, but I wasn't sure of the option to 
choose when filing the issue.  Just wanted to make sure it was on your radar.  
Already following your workaround.  Thanks for the rapid response!

Original comment by mmatc...@gmail.com on 10 Oct 2013 at 5:02

GoogleCodeExporter commented 9 years ago 
No worries. I appreciate you coming to me. I'd file this in the Kali bug 
tracker though.

Original comment by rsmu...@gmail.com on 10 Oct 2013 at 5:04

GoogleCodeExporter commented 9 years ago 
Done!

Original comment by mmatc...@gmail.com on 10 Oct 2013 at 5:30

GoogleCodeExporter commented 9 years ago 
Just wanted to update you with what I received back from filing the report at 
Kali's bug tracker.

"You don't need to pass the full path to teamserver. All binaries in Kali are in
the system path.

root@kalitest32:~# teamserver 172.16.79.135 s3cr3t
[*] Generating X509 certificate and keystore (for SSL)
[*] Starting RPC daemon
[*] MSGRPC starting on 127.0.0.1:55554 (NO SSL):Msg...
[*] MSGRPC backgrounding at 2013-10-11 08:11:00 -0600...
[*] sleeping for 20s (to let msfrpcd initialize)"

So it looks like in Kali 1.0.5 we can reference teamserver directly as a 
binary.  I just tested it myself, and it works!

Original comment by mmatc...@gmail.com on 11 Oct 2013 at 2:24

GoogleCodeExporter commented 9 years ago 
Thanks. I took a look at this and I can confirm that Kali is correct. So your 
Kali environment is jacked up. Early Armitage Kali packages did not have this 
work around in them. I recommend that you apt-get install update ; apt-get 
install armitage and see if that fixes it for you.

Original comment by rsmu...@gmail.com on 11 Oct 2013 at 4:05