Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After update to r12214(msf) Armitage got vey very slow! #49

Closed
GoogleCodeExporter opened this issue Mar 15, 2015 · 3 comments
Closed

After update to r12214(msf) Armitage got vey very slow! #49

GoogleCodeExporter opened this issue Mar 15, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Armitage with a very very slow performance on a non VM box
2. Mouse right clicks takes forever for example to use the stack function
3. Host menu functions take forever to transmit the gui example MFS scans popup 
requiring network segmentation input take a long time to appear.

What is the expected output? What do you see instead?
This happened in ubuntu meerkat 10.10 Linux ptcasnxpt1079 2.6.35-25-generic 
#44-Ubuntu SMP Fri Jan 21 17:40:44 UTC 2011 x86_64 GNU/Linux
and on a sandbox environment also after performing the msfupdate. After the 
update things got complicated as within the VM BT4Rc2 and within Meerkat Ubuntu.


What version of Metasploit are you using (type: svn info)? On which
operating system?
version  =[ metasploit v3.7.0-dev [core:3.7 api:1.0] +[ svn r12214 updated 
today (2011.04.01)


Which database are you using?
Postgresql



Please provide any additional information below.





Original issue reported on code.google.com by str...@gmail.com on 2 Apr 2011 at 12:45

@GoogleCodeExporter
Copy link
Author

This sounds like an issue with your host computer or guest VM not having enough 
ram.

Original comment by rsmu...@gmail.com on 2 Apr 2011 at 3:51

  • Changed state: Invalid

@GoogleCodeExporter
Copy link
Author

Never mind, I found the cause. It's Metasploit's April Fools day joke. I guess 
it's on us. Set the environment variable NOFOOL to 1. Try:

export NOFOOL=1

Put that in your ~/.bashrc file. This will disable the April Fools day joke and 
return Armitage's performance to normal. Optionally, wait until tonight for the 
joke to be taken out of the codebase.

Original comment by rsmu...@gmail.com on 2 Apr 2011 at 3:18

@GoogleCodeExporter
Copy link
Author

^_^, well that explains why the vmstat, iostat, top, snoop, strace and tcpdump 
were giving me the right values.... was like, wtf.....

Thanks again man and congrats for the awesome work here with Armitage. Its a 
nice masterpiece of code. Hopefully ill be able to provide the community also 
with a nice distributed system based for my thesis.

Original comment by str...@gmail.com on 2 Apr 2011 at 10:04

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant