Project

General

Profile

Actions

Bug #10627

closed

gem update fails with a certificate verification error

Added by thany (Martijn Saly) over 6 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
ruby -v:
ruby 2.1.5p273 (2014-11-13 revision 48405) [x64-mingw32]
[ruby-core:67010]

Description

Whenever I execute gem update or gem update --system it returns this error:

ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
    SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (https://api.rubygems.org/specs.4.8.gz)

This is on Ruby 2.1.5 with Gem 2.4.2 on Windows 7 x64.
I'm using the x64 version from here: http://rubyinstaller.org/downloads/

This is 100% reproducible, in a normal and in an elevated command prompt.

Not sure if this is a security problem. I'm fairly sure this problem did not exist a couple of days ago, using the exact same client. This indicates there's a problem on the remote server, and not really on my end.


Related issues

Related to Ruby master - Bug #10596: gem install ssl failureRejected12/14/2014Actions

Updated by luislavena (Luis Lavena) over 6 years ago

  • Related to Bug #10596: gem install ssl failure added

Updated by luislavena (Luis Lavena) over 6 years ago

  • Status changed from Open to Rejected
  • Priority changed from 5 to Normal

This has been answered before:

This is caused by changes on SSL certificates used by rubygems.org.

Please read the following:

https://gist.github.com/luislavena/f064211759ee0f806c88

This is also covered in RubyInstaller's group, as sticky note and mentioned several times on RubyGems issue tracker on GitHub.

A search for the error message would have exposed also #10596 which was previous question about this.

Updated by thany (Martijn Saly) over 6 years ago

So now every new installation of Ruby & Gem has to undergo a tedious process of some sort, because someone decided it was a good idea to install an unsupported server certificate? Really?

Why is it not being fixed from your end?

Updated by luislavena (Luis Lavena) over 6 years ago

Martijn Saly wrote:

Why is it not being fixed from your end?

Have you read the background describing this?

Updated by thany (Martijn Saly) over 6 years ago

Frankly, no. And I shouldn't have to. I'm a user of gems, not a developer of one (or the system for that matter). To be blunt: I "just" need it to work.

Updated by thany (Martijn Saly) over 6 years ago

Please note, I just freshly installed Ruby 2.1.5 on a different machine. Same problem.

I shouldn't have to manually solve problems like this on a virgin installation!
Please un-reject this issue and provide a proper solution.

Actions

Also available in: Atom PDF