[Bug 276006] metasploit: msfconsole fails to start on fresh install
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 276006] security/metasploit: msfconsole fails to start on fresh install"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 276006] security/metasploit: msfconsole fails to start on fresh install"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 276006] security/metasploit: msfconsole fails to start on fresh install"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 276006] security/metasploit: msfconsole fails to start on fresh install"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 276006] security/metasploit: msfconsole fails to start on fresh install"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 276006] security/metasploit: msfconsole fails to start on fresh install"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 276006] security/metasploit: msfconsole fails to start on fresh install"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 29 Dec 2023 23:56:07 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276006 Bug ID: 276006 Summary: metasploit: msfconsole fails to start on fresh install Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: unitrunker@gmail.com On 14.0-RELEASE with no ruby or metasploit installed ... # pkg install metasploit and, after successful installation ... # msfconsole /usr/local/lib/ruby/gems/3.1/gems/bundler-2.4.20/lib/bundler/resolver.rb:116:in `rescue in solve_versions': Could not find compatible versions (Bundler::SolveFailure) Because every version of metasploit-framework depends on octokit ~> 4.0 and octokit ~> 4.0 could not be found in locally installed gems, metasploit-framework cannot be used. So, because Gemfile depends on metasploit-framework >= 0, version solving has failed. from /usr/local/lib/ruby/gems/3.1/gems/bundler-2.4.20/lib/bundler/resolver.rb:79:in `solve_versions' from /usr/local/lib/ruby/gems/3.1/gems/bundler-2.4.20/lib/bundler/resolver.rb:32:in `start' from /usr/local/lib/ruby/gems/3.1/gems/bundler-2.4.20/lib/bundler/definition.rb:570:in `start_resolution' from /usr/local/lib/ruby/gems/3.1/gems/bundler-2.4.20/lib/bundler/definition.rb:301:in `resolve' from /usr/local/lib/ruby/gems/3.1/gems/bundler-2.4.20/lib/bundler/definition.rb:523:in `materialize' from /usr/local/lib/ruby/gems/3.1/gems/bundler-2.4.20/lib/bundler/definition.rb:200:in `specs' from /usr/local/lib/ruby/gems/3.1/gems/bundler-2.4.20/lib/bundler/definition.rb:266:in `specs_for' The 'octokit' error message is nonsense. # gem list | grep 'octo' octokit (8.0.0, 7.2.0) I don't know ruby well enough to chase this any further. -- You are receiving this mail because: You are the assignee for the bug.