pentoo / pentoo-historical

read-only historical backup of pentoo from googlecode
https://code.google.com/p/pentoo/
2 stars 1 forks source link

metasploit ( msf ) from pentoo does not run #169

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. msfconsole from pentoo spews errors; msfconsole from github works as 
expected after "bundle install"

Here are the typical startup messages / error after running Pentoo msfconsole:

WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically 
loaded 2.9.1
DEPRECATION WARNING: Using #scope without passing a callable object is 
deprecated. For example `scope :red, where(color: 'red')` should be changed to 
`scope :red, -> { where(color: 'red') }`. There are numerous gotchas in the 
former usage and it makes the implementation more complicated and buggy. (If 
you prefer, you can just define a class method named `self.red`.). (called from 
require at 
/usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:112)
DEPRECATION WARNING: Using #scope without passing a callable object is 
deprecated. For example `scope :red, where(color: 'red')` should be changed to 
`scope :red, -> { where(color: 'red') }`. There are numerous gotchas in the 
former usage and it makes the implementation more complicated and buggy. (If 
you prefer, you can just define a class method named `self.red`.). (called from 
require at 
/usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:112)
DEPRECATION WARNING: Using #scope without passing a callable object is 
deprecated. For example `scope :red, where(color: 'red')` should be changed to 
`scope :red, -> { where(color: 'red') }`. There are numerous gotchas in the 
former usage and it makes the implementation more complicated and buggy. (If 
you prefer, you can just define a class method named `self.red`.). (called from 
require at 
/usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:112)
DEPRECATION WARNING: Using #scope without passing a callable object is 
deprecated. For example `scope :red, where(color: 'red')` should be changed to 
`scope :red, -> { where(color: 'red') }`. There are numerous gotchas in the 
former usage and it makes the implementation more complicated and buggy. (If 
you prefer, you can just define a class method named `self.red`.). (called from 
require at 
/usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:112)
DEPRECATION WARNING: Using #scope without passing a callable object is 
deprecated. For example `scope :red, where(color: 'red')` should be changed to 
`scope :red, -> { where(color: 'red') }`. There are numerous gotchas in the 
former usage and it makes the implementation more complicated and buggy. (If 
you prefer, you can just define a class method named `self.red`.). (called from 
require at 
/usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:112)
DEPRECATION WARNING: Using #scope without passing a callable object is 
deprecated. For example `scope :red, where(color: 'red')` should be changed to 
`scope :red, -> { where(color: 'red') }`. There are numerous gotchas in the 
former usage and it makes the implementation more complicated and buggy. (If 
you prefer, you can just define a class method named `self.red`.). (called from 
require at 
/usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:112)
/usr/local/lib64/ruby/gems/1.9.1/gems/activemodel-4.0.0/lib/active_model/depreca
ted_mass_assignment_security.rb:17:in `attr_accessible': `attr_accessible` is 
extracted out of Rails into a gem. Please use new recommended protection model 
for params(strong_parameters) or add `protected_attributes` to your Gemfile to 
use old one. (RuntimeError)
    from /usr/local/lib64/ruby/gems/1.9.1/gems/metasploit_data_models-0.16.5/app/models/mdm/module/action.rb:14:in `<class:Action>'
    from /usr/local/lib64/ruby/gems/1.9.1/gems/metasploit_data_models-0.16.5/app/models/mdm/module/action.rb:1:in `<top (required)>'
    from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:112:in `require'
    from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:112:in `require'
    from /usr/lib64/metasploit9999/lib/fastlib.rb:374:in `require'
    from /usr/local/lib64/ruby/gems/1.9.1/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:228:in `block in require'
    from /usr/local/lib64/ruby/gems/1.9.1/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:213:in `load_dependency'
    from /usr/local/lib64/ruby/gems/1.9.1/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:228:in `require'
    from /usr/local/lib64/ruby/gems/1.9.1/gems/metasploit_data_models-0.16.5/lib/metasploit_data_models/models.rb:17:in `block in require_models'
    from /usr/local/lib64/ruby/gems/1.9.1/gems/metasploit_data_models-0.16.5/lib/metasploit_data_models/models.rb:16:in `glob'
    from /usr/local/lib64/ruby/gems/1.9.1/gems/metasploit_data_models-0.16.5/lib/metasploit_data_models/models.rb:16:in `require_models'
    from /usr/lib64/metasploit9999/lib/msf/core/db_manager.rb:106:in `initialize_database_support'
    from /usr/lib64/metasploit9999/lib/msf/core/db_manager.rb:78:in `initialize'
    from /usr/lib64/metasploit9999/lib/msf/core/framework.rb:88:in `new'
    from /usr/lib64/metasploit9999/lib/msf/core/framework.rb:88:in `initialize'
    from /usr/lib64/metasploit9999/lib/msf/base/simple/framework.rb:73:in `new'
    from /usr/lib64/metasploit9999/lib/msf/base/simple/framework.rb:73:in `create'
    from /usr/lib64/metasploit9999/lib/msf/ui/console/driver.rb:82:in `initialize'
    from /usr/bin/msfconsole:169:in `new'
    from /usr/bin/msfconsole:169:in `<main>'

Original issue reported on code.google.com by willard....@gmail.com on 18 Aug 2013 at 6:35

GoogleCodeExporter commented 9 years ago
ZC this is not reliable and not cool.
We need to switch to a snapshot ebuild instead of live version.

Original comment by blshkv on 18 Aug 2013 at 8:55

GoogleCodeExporter commented 9 years ago
You have incompatible activesupport 4 installed.  It isn't in gentoo, I have no 
idea how you broke your system but I'd remove the garbage you installed in 
/usr/local/lib64/ruby/gems/1.9.1/gems/ and it likely works fine.   Unable to 
replicate.

Original comment by sidhayn on 18 Aug 2013 at 9:17

GoogleCodeExporter commented 9 years ago
I suppose that's what I get for doing "bundle install" in a dev copy of 
metasploit-framework (from Git) followed by a 'gem update'.

Easy enough to replicate should you so desire to go that route...

Or, consider it bogus otherwise.  I'm not picky.  Just annoyed that I so easily 
broke Pentoo Metasploit...

Original comment by willard....@gmail.com on 19 Aug 2013 at 1:46

GoogleCodeExporter commented 9 years ago
I agree with ZC, you should not install anything manually because it will break 
your system soon or later. That /usr/local directory shouldn't be there.

Just in case, I'll do additional testing and check if msf works with slotted 
activesupport so it won't break it in future.

ps. you can get rid of the first nokogiri warning by running "emerge -1 
nokogiri" (-1 because it's a dep and you don't want it to be in your world file)

Original comment by blshkv on 19 Aug 2013 at 1:57

GoogleCodeExporter commented 9 years ago
"Testing" results attached.

Original comment by willard....@gmail.com on 20 Aug 2013 at 3:41

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by blshkv on 23 Aug 2013 at 10:53

GoogleCodeExporter commented 9 years ago
Issue 172 has been merged into this issue.

Original comment by sidhayn on 25 Aug 2013 at 4:10

GoogleCodeExporter commented 9 years ago
Issue 172 has been merged into this issue.

Original comment by blshkv on 25 Aug 2013 at 4:14