-
Notifications
You must be signed in to change notification settings - Fork 302
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
RubyGems.org patched for Poodle SSLv3 (CVE-2014-3566) breaks Windows gem commands #241
Comments
@ferventcoder is a local patch? a new release of RubyGems? I'm not fully understand what RubyInstaller has to do with this, if is RubyGems or Ruby issues needs to be reported to them. Can you clarify? Thank you. |
@luislavena giving you a heads up. Not sure of what/where yet, but I think rubygems.org just patched their servers. |
Does the workaround suggested here work? #209 (comment) |
@ferventcoder then this needs to be reported to RubyGems, not RubyInstaller (we don't alter or modify Ruby or RubyGems beyond packaging, as described in #39) |
@luislavena right on, was looking for verification on this. I will follow up with Nick et. al. |
I can confirm the workaround works adding this to your ~/.gemrc file:
|
Closing to report to right repo. |
Are there any plans to update Rubyinstaller to incorporate the changes to gems? Right now Rubyinstaller ships a non-working gem version. |
with the error: C:\>ruby --version ruby 2.1.5p273 (2014-11-13 revision 48405) [i386-mingw32] C:\>gem install bundler ERROR: Could not find a valid gem 'bundler' (>= 0), here is why: Unable to download data from https://rubygems.org/ - SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (https://api.rubygems.org/latest_specs.4.8.gz) |
@MikaelSmith @joshcooper as mentioned above, this issue as nothing to do with RubyInstaller. Please take a look to the following guide in order to manually patch Trust certs in your installation of RubyGems: |
How is the version of Rubygems that appears in the installer determined? It seems to ship with version 2.2.2; including version 2.4.4 would fix that, and I assumed choosing the version is part of building RubyInstaller. |
My mistake, it looks like ruby itself vendors rubygems at 2.2.2. So I guess this will be addressed in a future Ruby version. |
Answers to your previous post and new questions:
RubyInstaller versions are in sync with Ruby versions, if a new version of Ruby goes out, a new version of RubyInstaller will go out. We don't patch or alter Ruby or the provided components. Please see CONTRIBUTING We release individual versions like updates to OpenSSL, zlib and such that can be freely updated after the installation. On each of those releases we bump versions in RubyInstaller so next releases ship that without manual installation.
This issue is about POODLE, which had nothing to do with RubyInstaller. RubyGems ships with Ruby, and RubyInstaller ships Ruby, but we don't modify the version of RubyGems on releases. And we don't perform releases of RubyInstaller simply because RubyGems needs patching (unless of course there is a Ruby release). Please note that it takes considerable amount of effort to perform a new release of RubyInstaller, not to mention go and patch every single problem out there to make things work.
RubyGems 2.4. is broken on Windows, as reported several times to RubyGems and RubyInstaller mailing list (and here):
Until that is fixed I cannot recommend upgrade to RubyGems 2.4 I personally don't have the time to go and fix those issues, but will be able to provide assistance and guidance to those willing to take the challenge. Hope this makes it more clear and while I understand your concerns, this approach to handle releases will not be changed. We dealt in the past with patches and such and the stress around that was too high. Not only I have to deal with work, life and other, but personal accusations to my inbox (not your case) caused by RubyGems, false positives of virus reports or weird gems not working. https://groups.google.com/d/topic/rubyinstaller/VoV0bOqMV4M/discussion I've been doing this for the past 7 years, and patching gems for Windows compatibility for almost 9 years. If someone believes that can do it better, please step up and get this fixed so everybody benefits. I for sure will love to take a break when Ruby team releases versions on 25th December and I have to cook new releases every year after Xmas. |
Thanks, and sorry for the tone. It's an irritating issue, and it took me a little bit to understand how packaging is being done. |
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3566
Ruby 1.9.3
Ruby 2.0.0
Ruby 2.1.3
The text was updated successfully, but these errors were encountered: