Add check method
Merge pull request #28 from rapid7/feature/MSP-9726/smart_hashdump

Feature/msp 9726/smart hashdump

MSP-9726 #land
Changed message
Merge branch 'staging/electro-release' into feature/MSP-9678/pop3-login-scanner
Merge pull request #29 from rapid7/feature/MSP-9739/mremote_refactor

Feature/msp 9739/mremote refactor

MSP-9739 #land
Land #3413, improved FileDropper cleanup message
Land #3406, indeces_enum -> indices_enum
Merge branch 'master' into staging/electro-release

Conflicts:
	.ruby-version
refactor smartftp post module

refactor the smartftp credential post module to use
Metasploit::Credential
Explicitly require gem dependencies

MSP-9653
Add module paths from paths['modules'] from Rails app and engines

MSP-9653

Allow rails engines (and other applications, like
Metasploit::Pro::Engine::Application) to define their own module paths
using the paths['modules'] entry for Rails Applications/Engines.
msfenv compatibility with Pro

MSP-9653

lib/msfenv.rb should only load the framework environment to initialize
Metasploit::Framework::Application if a Rails.application is not
defined, otherwise it will clash with the Rails application in prosvc.
Msf::DBManager#connection_established?

MSP-9653

Calling `ActiveRecord::Base.establish_connection`, followed by
`ActiveRecord::Base.connected?` returns false unless some other code
requires a connection to be checked out first.  The correct way to check
if the spec passed to `ActiveRecord::Base.establish_connection` is to
checkout a connection and then ask if it is active.
`Msf::DBManager#connection_established?` does the checkout, active check
and checkin, and should be used in place of
`ActiveRecord::Base.connected?` and
`ActiveRecord::Base.connection_pool.connected?`.
`Msf::DBManager#active` should still be used as it also checks for
adapter/driver usability and that migrations have run.
Gem version

MSP-9653

Move version information to standard location for gems.
Extra common engine and fix default encoding

MSP-9653

Extra config and initializers that can we shared between
Metasploit::Framework::Application and the future
Metasploit::Framework::Engine.  Move the default encoding setup from
lib/msf/sanity.rb to a before_initialize callback for the shared config
so that gems, like gherkin that depend on the utf-8 default internal
encoding can be loaded.
Metasploit::Framework::Engine

MSP-9653

Rails::Engine version of Metasploit::Framework::Application that can be
used by downstream projects, like Pro to get the shared behaviors, like
modules path adding, meterpreter extension merging, and binary default
encoding.
Gemspec

MSP-9653

Add gemspec for metasploit-framework so that pro can declare it as a
proper dependency.  DO NOT release metasploit-framework to rubygems: it
is 47 MB and would be not be nice to their servers.
I prefer "bruteforce" to "brute force" for search

Just makes it easier to search for, since it's an industry term of art.
Merge pull request #31 from rapid7/feature/MSP-9728/coreftp

refactor coreFTP post module

MSP-9728 #land
Make print/descs/case consistent