-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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.
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
Beef starting error, possibly not beef but rvm/ruby related... #1377
Comments
Make sure you |
There is something wrong with my rvm/ruby setup but that's apparently what I don't understand. If I try
Mysterious for the noob is that other ruby related tools like msfconsole, bettercap, ... are working. |
Thanks for providing a detailed report. Looks like an issue with your RVM. Try tweaking the version of Ruby in Metasploit uses 2.3.3. Try also cloning BeEF from github and doing a Edit Also try removing the |
Hi @crowstone - any luck with this? |
|
@bcoles |
Environment
What version/revision of BeEF are you using?
Latest git clone (2017/03/15)
On what version of Ruby?
ruby 2.3.3p222 (2016-11-21) [x86_64-linux-gnu]
-e:1:in
<main>': undefined local variable or method
rsion' for main:Object (NameError)On what browser?
not relevant, Firefox ESR
On what operating system?
Kali Rolling
Configuration
Are you using a non-default configuration?
no
Have you enabled or disabled any BeEF extensions?
no
Summary
Please provide a summary of the issue.
Starting Beef Framework dumps me this error:
Expected Behaviour
What was the expected result?
Actual Behaviour
What was the actual result?
Steps to Reproduce
./beef
Additional Information
I ran beef without any problems for months and I'm sure this error is not directly related to beef. I updated kali with apt-get update/upgrade/dist-upgrade, git pull, and gem update.
Since then I got these error messages. I tried to repair rvm, reinstall beef, no success.
Since I'm a total ruby/rvm noob I hope to get some help here. Looks like a misconfiguration problem since the /usr/share/ruby-addressable/ folder is obviously not the right place to find the gem...
The text was updated successfully, but these errors were encountered: