View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003112 | Kali Linux | Kali Package Bug | public | 2016-03-02 13:56 | 2016-03-16 05:42 |
Reporter | busterb | Assigned To | rhertzog | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 2016.1 | ||||
Fixed in Version | 2016.2 | ||||
Summary | 0003112: bundler 1.10.6 packaged with kali-rolling has a bug running the latest metasploit-framework | ||||
Description | If a user checks out metasploit-framework from git, and uses ruby 2.2.4 and bundler 1.10.6 packaged currently with kali-rolling, bundler fails with a backtrace: /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in | ||||
Steps To Reproduce | git clone http://metasploit-framework root@kali:~/metasploit-framework# ./msfconsole | ||||
Additional Information | Despite our warnings to users that they should be using isolated gemsets, folks seem to want to have checking out the latest framework on Kali 'just work', and it looks like upgrading bundler should do it. I suppose we could also suggest to users of kali to set GEM_PATH specially, or use the special ruby wrapper supplied with kali-rolling: ~/metasploit-framework# /usr/share/metasploit-framework/ruby ./msfconsole We do recommend setting up rvm and having an isolated gemset when doing development, but it would be nice if kali-rolling is tracking the latest bundler to get this bug fixed. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2016-03-02 13:56 | busterb | New Issue | |
2016-03-02 15:16 | rhertzog | Note Added: 0004804 | |
2016-03-02 15:16 | rhertzog | Status | new => closed |
2016-03-02 15:16 | rhertzog | Assigned To | => rhertzog |
2016-03-02 15:16 | rhertzog | Resolution | open => fixed |
2016-03-02 15:16 | rhertzog | Fixed in Version | => 2016.2 |