Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Several Errors After Updating #16853

Closed
init5-SF opened this issue Aug 2, 2022 · 4 comments
Closed

Several Errors After Updating #16853

init5-SF opened this issue Aug 2, 2022 · 4 comments
Labels
bug openssl3 Tracking issues related to OpenSSL 3's backwards breaking changes

Comments

@init5-SF
Copy link

init5-SF commented Aug 2, 2022

Steps to reproduce

I just did apt update and apt upgrade, metasploit was one of the upgradable packages.

Were you following a specific guide/tutorial or reading documentation?

No

Expected behavior

Running msfconsole or msfvenom should behave normally

Current behavior

I get these errors when I use msfconsole or msfvenom

/usr/share/metasploit-framework/vendor/bundle/ruby/3.0.0/gems/hrr_rb_ssh-0.4.2/lib/hrr_rb_ssh/transport/server_host_key_algorithm/ecdsa_sha2_nistp256.rb:11: warning: already initialized constant HrrRbSsh::Transport::ServerHostKeyAlgorithm::EcdsaSha2Nistp256::NAME
/usr/share/metasploit-framework/vendor/bundle/ruby/3.0.0/gems/hrr_rb_ssh-0.4.2/lib/hrr_rb_ssh/transport/server_host_key_algorithm/ecdsa_sha2_nistp256.rb:11: warning: previous definition of NAME was here
/usr/share/metasploit-framework/vendor/bundle/ruby/3.0.0/gems/hrr_rb_ssh-0.4.2/lib/hrr_rb_ssh/transport/server_host_key_algorithm/ecdsa_sha2_nistp256.rb:12: warning: already initialized constant HrrRbSsh::Transport::ServerHostKeyAlgorithm::EcdsaSha2Nistp256::PREFERENCE
/usr/share/metasploit-framework/vendor/bundle/ruby/3.0.0/gems/hrr_rb_ssh-0.4.2/lib/hrr_rb_ssh/transport/server_host_key_algorithm/ecdsa_sha2_nistp256.rb:12: warning: previous definition of PREFERENCE was here
/usr/share/metasploit-framework/vendor/bundle/ruby/3.0.0/gems/hrr_rb_ssh-0.4.2/lib/hrr_rb_ssh/transport/server_host_key_algorithm/ecdsa_sha2_nistp256.rb:13: warning: already initialized constant HrrRbSsh::Transport::ServerHostKeyAlgorithm::EcdsaSha2Nistp256::IDENTIFIER
/usr/share/metasploit-framework/vendor/bundle/ruby/3.0.0/gems/hrr_rb_ssh-0.4.2/lib/hrr_rb_ssh/transport/server_host_key_algorithm/ecdsa_sha2_nistp256.rb:13: warning: previous definition of IDENTIFIER was here
/usr/share/metasploit-framework/vendor/bundle/ruby/3.0.0/gems/hrr_rb_ssh-0.4.2/lib/hrr_rb_ssh/transport/server_host_key_algorithm/ecdsa_sha2_nistp256.rb:11: warning: already initialized constant HrrRbSsh::Transport::ServerHostKeyAlgorithm::EcdsaSha2Nistp256::NAME
/usr/share/metasploit-framework/vendor/bundle/ruby/3.0.0/gems/hrr_rb_ssh-0.4.2/lib/hrr_rb_ssh/transport/server_host_key_algorithm/ecdsa_sha2_nistp256.rb:11: warning: previous definition of NAME was here
/usr/share/metasploit-framework/vendor/bundle/ruby/3.0.0/gems/hrr_rb_ssh-0.4.2/lib/hrr_rb_ssh/transport/server_host_key_algorithm/ecdsa_sha2_nistp256.rb:12: warning: already initialized constant HrrRbSsh::Transport::ServerHostKeyAlgorithm::EcdsaSha2Nistp256::PREFERENCE
/usr/share/metasploit-framework/vendor/bundle/ruby/3.0.0/gems/hrr_rb_ssh-0.4.2/lib/hrr_rb_ssh/transport/server_host_key_algorithm/ecdsa_sha2_nistp256.rb:12: warning: previous definition of PREFERENCE was here
/usr/share/metasploit-framework/vendor/bundle/ruby/3.0.0/gems/hrr_rb_ssh-0.4.2/lib/hrr_rb_ssh/transport/server_host_key_algorithm/ecdsa_sha2_nistp256.rb:13: warning: already initialized constant HrrRbSsh::Transport::ServerHostKeyAlgorithm::EcdsaSha2Nistp256::IDENTIFIER
/usr/share/metasploit-framework/vendor/bundle/ruby/3.0.0/gems/hrr_rb_ssh-0.4.2/lib/hrr_rb_ssh/transport/server_host_key_algorithm/ecdsa_sha2_nistp256.rb:13: warning: previous definition of IDENTIFIER was here

Metasploit version

Framework: 6.2.9-dev
Console : 6.2.9-dev

Additional Information

Module/Datastore

The following global/module datastore, and database setup was configured before the issue occurred:

Collapse 
[framework/core]
loglevel=3

Database Configuration

The database contains the following information:

Collapse 
Session Type: postgresql selected, no connection

History

The following commands were ran during the session and before this issue occurred:

Collapse 
2000   version
2001   debug
2002   set loglevel 3
2003   clear
2004   debug

Framework Errors

The following framework errors occurred before the issue occurred:

Collapse 
[08/02/2022 19:45:31] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:45:31] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:45:34] [e(0)] core: Failed to connect to the database: No database YAML file
[08/02/2022 19:45:35] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:45:35] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:45:35] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:52:45] [e(0)] core: Failed to connect to the database: No database YAML file
[08/02/2022 19:52:47] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:52:47] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:52:47] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0

Web Service Errors

The following web service errors occurred before the issue occurred:

Collapse 
msf-ws.log does not exist.

Framework Logs

The following framework logs were recorded before the issue occurred:

Collapse 
[04/02/2022 16:06:10] [w(0)] core: 	/usr/share/metasploit-framework/modules/auxiliary/scanner/msmail/exchange_enum.go
[04/02/2022 16:06:10] [w(0)] core: 	/usr/share/metasploit-framework/modules/auxiliary/scanner/msmail/onprem_enum.go
[04/02/2022 16:06:10] [d(0)] core: HistoryManager.push_context name: :msfconsole
[04/02/2022 16:06:30] [d(0)] core: HistoryManager.pop_context name: :msfconsole
[04/12/2022 17:46:48] [e(0)] core: Failed to connect to the database: No database YAML file
[04/12/2022 17:46:48] [d(0)] core: Updated user based module store
[04/12/2022 17:46:51] [d(0)] core: HistoryManager.push_context name: :msfconsole
[04/12/2022 17:46:51] [e(0)] core: Failed to connect to the database: No database YAML file
[04/12/2022 17:47:15] [d(0)] core: HistoryManager.pop_context name: :msfconsole
[04/12/2022 17:48:46] [e(0)] core: Failed to connect to the database: No database YAML file
[04/12/2022 17:48:48] [d(0)] core: HistoryManager.push_context name: :msfconsole
[04/12/2022 17:48:52] [e(0)] core: Failed to connect to the database: No database YAML file
[04/12/2022 17:48:59] [d(0)] core: HistoryManager.pop_context name: :msfconsole
[04/15/2022 17:52:13] [e(0)] core: Failed to connect to the database: No database YAML file
[04/15/2022 17:52:20] [e(0)] core: Failed to connect to the database: No database YAML file
[04/15/2022 17:52:22] [d(0)] core: HistoryManager.push_context name: :msfconsole
[04/15/2022 17:52:36] [d(0)] core: HistoryManager.pop_context name: :msfconsole
[04/20/2022 12:55:00] [e(0)] core: Failed to connect to the database: No database YAML file
[04/21/2022 17:02:24] [d(0)] core: Updated user based module store
[04/21/2022 17:02:25] [e(0)] core: Failed to connect to the database: No database YAML file
[04/21/2022 17:02:33] [e(0)] core: Failed to connect to the database: No database YAML file
[04/21/2022 17:02:35] [d(0)] core: HistoryManager.push_context name: :msfconsole
[04/21/2022 17:02:38] [d(0)] core: HistoryManager.pop_context name: :msfconsole
[04/23/2022 15:47:49] [e(0)] core: Failed to connect to the database: No database YAML file
[05/16/2022 19:02:54] [d(0)] core: Updated user based module store
[05/16/2022 19:02:56] [e(0)] core: Failed to connect to the database: No database YAML file
[05/16/2022 19:03:00] [e(0)] core: Failed to connect to the database: No database YAML file
[05/16/2022 19:03:04] [d(0)] core: HistoryManager.push_context name: :msfconsole
[05/16/2022 19:03:08] [d(0)] core: HistoryManager.pop_context name: :msfconsole
[05/30/2022 19:47:16] [e(0)] core: Failed to connect to the database: No database YAML file
[05/30/2022 19:58:09] [e(0)] core: Failed to connect to the database: No database YAML file
[05/30/2022 19:58:26] [e(0)] core: Failed to connect to the database: No database YAML file
[05/30/2022 20:00:02] [e(0)] core: Failed to connect to the database: No database YAML file
[05/30/2022 20:00:04] [e(0)] core: Failed to connect to the database: No database YAML file
[08/02/2022 19:45:29] [e(0)] core: Failed to connect to the database: No database YAML file
[08/02/2022 19:45:29] [d(0)] core: Updated user based module store
[08/02/2022 19:45:31] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:45:31] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:45:31] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:45:32] [d(0)] core: HistoryManager.push_context name: :msfconsole
[08/02/2022 19:45:34] [e(0)] core: Failed to connect to the database: No database YAML file
[08/02/2022 19:45:35] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:45:35] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:45:35] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:46:15] [d(0)] core: HistoryManager.pop_context name: :msfconsole
[08/02/2022 19:52:45] [e(0)] core: Failed to connect to the database: No database YAML file
[08/02/2022 19:52:47] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:52:47] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:52:47] [e(0)] core: OpenSSL::PKey::PKeyError pkeys are immutable on OpenSSL 3.0
[08/02/2022 19:52:49] [d(0)] core: HistoryManager.push_context name: :msfconsole

Web Service Logs

The following web service logs were recorded before the issue occurred:

Collapse 
msf-ws.log does not exist.

Version/Install

The versions and install method of your Metasploit setup:

Collapse 
Framework: 6.2.9-dev
Ruby: ruby 3.0.4p208 (2022-04-12 revision 3fa771dded) [x86_64-linux-gnu]
OpenSSL: OpenSSL 3.0.3 3 May 2022
Install Root: /usr/share/metasploit-framework
Session Type: postgresql selected, no connection
Install Method: Other - Please specify
@init5-SF init5-SF added the bug label Aug 2, 2022
@gwillcox-r7
Copy link
Contributor

Those are warnings not errors. They should not prevent normal operation of Metasploit.

@adfoster-r7
Copy link
Contributor

Closing as a duplicate of #16818

These are warnings related to OpenSSL 3 and can be ignored 👍

@adfoster-r7 adfoster-r7 added the openssl3 Tracking issues related to OpenSSL 3's backwards breaking changes label Aug 2, 2022
@init5-SF
Copy link
Author

init5-SF commented Aug 3, 2022

@adfoster-r7 Thanks for the info, is there a way to fix it and prevent those warnings?

@adfoster-r7
Copy link
Contributor

adfoster-r7 commented Aug 3, 2022 •
edited
Loading

For now they can be ignored, and we should have the warnings fixed in the next release or so 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug openssl3 Tracking issues related to OpenSSL 3's backwards breaking changes
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@init5-SF @adfoster-r7 @gwillcox-r7