Turn off Ruby deprecation warnings for all users

[dwelch-r7]

Turns off warnings for all users, this is a temporary measure to limit the confusion we're seeing with end users on ruby 2.7.0 that now produces several warnings.
There will be another PR up soon to enable warnings only when msf is being used in a development environment

• Switch to ruby 2.7.0
• Start up msfconsole
• Observe the warnings
• Checkout this branch
• Start up msfconsole
• Warnings should be gone

[adfoster-r7]

Would any of the other tools be impacted, like msfvenom etc?

[dwelch-r7]

I don't believe this should affect any other tools no
do you think we should be disabling warnings from other tools? I don't think we've had any issues from that (yet)

[adfoster-r7]

In some scenarios msfvenom loads msf, which will trigger warnings:

$ ruby --version
ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-darwin18]
$ bundle exec ruby ./msfvenom -p windows/meterpreter/reverse_tcp LHOST=127.0.0.1 --encrypt rc4 --encrypt-key thisisakey -f c
/Users/user/.rvm/gems/ruby-2.7.0/gems/activerecord-4.2.11.1/lib/active_record/connection_adapters/abstract_adapter.rb:84: warning: deprecated Object#=~ is called on Integer; it always returns nil
/Users/user/.rvm/gems/ruby-2.7.0/gems/activerecord-4.2.11.1/lib/active_record/connection_adapters/abstract_adapter.rb:84: warning: deprecated Object#=~ is called on Integer; it always returns nil

...

Other tools may also load msf

[adfoster-r7]

I'm good to land this change for now, and we can look into the other edgecases as part of the follow up work 👍

[dwelch-r7]

➜  metasploit-framework git:(turn-off-warnings) ✗ ./msfvenom -p windows/meterpreter/reverse_tcp LHOST=127.0.0.1 --encrypt rc4 --encrypt-key thisisakey -f c
/Users/dwelch/.rvm/gems/ruby-2.7.0@metasploit-framework/gems/activerecord-4.2.11.1/lib/active_record/connection_adapters/abstract_adapter.rb:84: warning: deprecated Object#=~ is called on Integer; it always returns nil
/Users/dwelch/.rvm/gems/ruby-2.7.0@metasploit-framework/gems/activerecord-4.2.11.1/lib/active_record/connection_adapters/abstract_adapter.rb:84: warning: deprecated Object#=~ is called on Integer; it always returns nil

just checked, it doesn't affect msfvenom, it's loading those files sure but not via the msfconsole file where I added the change

[adfoster-r7]

msfvenom loads msf directly here:

metasploit-framework/msfvenom

Lines 21 to 32 in 2dc26db

	def require_deps
	require 'msfenv'
	$:.unshift(ENV['MSF_LOCAL_LIB']) if ENV['MSF_LOCAL_LIB']
	require 'rex'
	require 'msf/ui'
	require 'msf/base'
	require 'msf/core/payload_generator'
	@framework_loaded = true
	end

I think that means that either the deprecated warning suppression needs to be in the entrypoints of our tools, or closer to the entrypoint of msf itself.

[adfoster-r7]

Confirmed that this no longer shows warnings with Ruby 2.7 on bootup, or later:

Master:

msf5 > irb
[*] Starting IRB shell...
[*] You are in the "framework" object

irb: warn: can't alias jobs from irb_jobs.
>> 123 =~ 'abc'
(irb):1: warning: deprecated Object#=~ is called on Integer; it always returns nil
=> nil

Branch:

msf5 > irb
[*] Starting IRB shell...
[*] You are in the "framework" object

irb: warn: can't alias jobs from irb_jobs.
>> 123 =~ 'abc'
=> nil

[adfoster-r7]

Release Notes

The msfconsole will no longer output ActiveRecord warning messages on start up when using Ruby 2.7.x