metasploit-framework/Rakefile

#!/usr/bin/env rake
require File.expand_path('../config/application', __FILE__)
require 'metasploit/framework/require'

# @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

Metasploit::Framework::Application.load_tasks
Metasploit::Framework::Spec::Constants.define_task
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'`

			# @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`
Log leaked constants and fail rake spec on leak MSP-11130 Instead of printing the leaked constants to stderr, log them to `log/leaked-constants.log`. In task action for spec, read `log/leaked-constants.log`. If it exists, print each leaked constants (and it appropriate it's module full name) and then exit with 1. If the file does not exist, do nothing. 2014-10-28 17:21:35 +01:00			`Metasploit::Framework::Spec::Constants.define_task`