github/metasploit-framework
1
Fork 0
mirror of https://github.com/rapid7/metasploit-framework synced 2024-10-29 18:07:27 +01:00
Code Releases Activity
b0f1b2a1f7
metasploit-framework/Rakefile

15 lines
641 B
Ruby
Raw Normal View History

Use railties to load Metasploit::Credential correctly MSP-9606 In order to support Metasploit::Credential correctly, metasploit-framework needs to support Metasploit::Concern, which does all its magic using a Rails::Engine initializer, so the easiest path is to make metasploit-framework be able to use Rails::Engines. To make Rails::Engine use Rails::Engine, make a dummy Rails::Application subclass so that all the initializers will be run when anything requires msfenv.
2014-05-12 22:03:51 +02:00
#!/usr/bin/env rake
require File.expand_path('../config/application', __FILE__)
Optionally require 'active_record/railtie` in Rakefile MSP-10905 Require in Rakefile so that db tasks are defined. Make it optionally so that `rake` doesn't error out when metasploit-framework installed with `bundle install --without db`.
2014-07-30 17:10:20 +02:00
require 'metasploit/framework/require'
Extract untested-payloads.log checker spec task action MSP-11145 Extract the spec task action which errored out if `log/untested-payloads.log` exists to `Metasploit::Framework::Spec::UntestedPayloads.define_task`.
2014-10-23 17:24:33 +02:00
require 'metasploit/framework/spec/untested_payloads'
Optionally require 'active_record/railtie` in Rakefile MSP-10905 Require in Rakefile so that db tasks are defined. Make it optionally so that `rake` doesn't error out when metasploit-framework installed with `bundle install --without db`.
2014-07-30 17:10:20 +02:00
# @note must be before `Metasploit::Framework::Application.load_tasks`
#
# define db rake tasks from activerecord if activerecord is in the bundle. activerecord could be not in the bundle if
# the user installs with `bundle install --without db`
Metasploit::Framework::Require.optionally_active_record_railtie
Refactor Msf::ModuleManager [Fixes #36737359] Refactor Msf::ModuleManager into concerns so its easier to understand and duplicate code can be made DRY. The refactoring also ensures that when loading from directories, Fastlibs, or reloading, the wrapper module will always be named so that activesupport/dependencies will function.
2012-10-01 20:09:30 +02:00
Use railties to load Metasploit::Credential correctly MSP-9606 In order to support Metasploit::Credential correctly, metasploit-framework needs to support Metasploit::Concern, which does all its magic using a Rails::Engine initializer, so the easiest path is to make metasploit-framework be able to use Rails::Engines. To make Rails::Engine use Rails::Engine, make a dummy Rails::Application subclass so that all the initializers will be run when anything requires msfenv.
2014-05-12 22:03:51 +02:00
Metasploit::Framework::Application.load_tasks
Fail `rake spec` if leak tracking unnecessary MSP-11130 Fail `rake spec` if `Metasploit::Framework::Spec::Constants::Each.configure!`'s `before(:each)` does not clean all leaked constants and if should be removed so that it does not interefore with future specs.
2014-10-30 15:37:17 +01:00
Metasploit::Framework::Spec::Constants.define_task
Extract untested-payloads.log checker spec task action MSP-11145 Extract the spec task action which errored out if `log/untested-payloads.log` exists to `Metasploit::Framework::Spec::UntestedPayloads.define_task`.
2014-10-23 17:24:33 +02:00
Metasploit::Framework::Spec::UntestedPayloads.define_task
Copy Permalink