search

Becram / pentoo

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

msfconsole stops running after running msfupdate #361

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Log in as root
2. Run msfconsole (to show it's working)
3. Run msfupdate (to update msg)
4. Run msfconsole, then error pops up

What is the expected output? What do you see instead?
I am expecting to see msfconsole text console but I get this on the command line

pentoo init.d#msfconsole
Something went wrong, please open a bug for metasploit on 
https://bugs.gentoo.org
There was a Errno:ENOENT while loading metasploit-framework.gemspec:
No such file or directory @ realpath_re - /root/.msf4/lib from 
/root/.msf4/metasploit-framework,genspec:10:in `realpath`

pentoo init.d# mkdir /root/.msf4/lib

pentoo init.d# msfconsole
Something went wrong, please open a bug for metasploit on 
https://bugs.gentoo.org
There was a LoadError while loading metasploit-framework.gemspec:
cannot load such file -- metasploit/framework/version from 
   /root/.msf4/metasploit-framework.gemspec:14:in `<main>`

Does it try to require a relative path? That's been removed in Ruby 1.9.

pentoo init.d#

What version of the product are you using? On what operating system?
3.7

Please provide any additional information below.

Original issue reported on code.google.com by sayh...@gmail.com on 12 Jul 2015 at 11:29

GoogleCodeExporter commented 9 years ago 
Well, at Pentoo, we don't allow tools to update themselves so do not any of 
these.
msfupdate is our hack to update env if i'm not wrong.

You can safely remove /root/.msf4 and follow our wiki to update all tools at 
one go.

Original comment by blshkv on 12 Jul 2015 at 3:52

GoogleCodeExporter commented 9 years ago 
1.) msfupdate is safe to use, but is it not in any way the upstream msfupdate.  
I completely hijacked it a very long time ago to perform a safe update.  So no 
problem there

2.) msf uses ruby21 right now, it's forced by the ebuild and loader scripts.

I'm entirely unable to replicate anything like this, but if I had to guess your 
eselect-metasploit is out of date, you should be on version 0.16.  If that is 
the case, please stop building things with --nodeps

Original comment by sidhayn on 12 Jul 2015 at 11:43