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.

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

Update "dev setup how to" to account for ruby 2.1.7 install error #6492

Closed
sn0wfa11 opened this issue Jan 22, 2016 · 5 comments
Closed

Update "dev setup how to" to account for ruby 2.1.7 install error #6492

sn0wfa11 opened this issue Jan 22, 2016 · 5 comments
Assignees
Labels

Comments

@sn0wfa11
Copy link
Contributor

Background

While setting up the dev environment for Kali Rolling that just came out today, I received an error installing Ruby 2.1.7. After some research (links here and here. I found out that openssl libs have been updated to drop support of sslv3 while Ruby is still using it. The error I received is exactly the same as in the links.

Update Suggestion

Install RVM

(From RVM's site)

gpg --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3`
\curl -sSL https://get.rvm.io | bash -s stable --autolibs=enabled

Configure Gnome Terminal to use RVM

"Same as is already present"

Install Ruby 2.1.7 with patch

wget https://github.com/ruby/ruby/commit/801e1fe46d83c856844ba18ae4751478c59af0d1.diff -O openssl.patch
rvm install --patch ./openssl.patch 2.1.7

gem install bundler

And go on from there.

I was able to get msfconsole running from my cloned fork at that point. Hope this helps someone else avoid the struggle.

@sn0wfa11 sn0wfa11 changed the title Update dev setup how to to account for ruby 2.1.7 install error Update "dev setup how to" to account for ruby 2.1.7 install error Jan 22, 2016
@sn0wfa11
Copy link
Contributor Author

Looks like "rake spec" doesn't like the patch as any ssl related item is failing...

@bcook-r7
Copy link
Contributor

Thanks! As a note, ruby 2.3.0 doesn't seem to have problems with this.

We probably also need to redo the SSL scanner, as it gets less useful all the time when it depends on what the system OpenSSL happens to have enabled.

@sn0wfa11
Copy link
Contributor Author

Thanks, I try using ruby 2.3.0 instead.

@bcook-r7 bcook-r7 self-assigned this Jan 22, 2016
@wchen-r7 wchen-r7 added the docs label Feb 2, 2016
@mathieujobin
Copy link

2.1.8 and 2.2.4 does not have this problem
you will need the same patch for older release 2.0.0, 2.1.7 and 2.2.3

@bcook-r7
Copy link
Contributor

We have since moved to Ruby 2.3.1, which can gracefully handle SSLv3 being missing. Thanks for the report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants