Path: | History.txt |
Last Update: | Fri Apr 27 23:20:44 +0000 2012 |
# coding: UTF-8
This release increases the security used when RubyGems is talking to an https server. If you use a custom RubyGems server over SSL, this release will cause RubyGems to no longer connect unless your SSL cert is globally valid.
You can configure SSL certificate usage in RubyGems through the :ssl_ca_cert and :ssl_verify_mode options in ~/.gemrc and /etc/gemrc. The recommended way is to set :ssl_ca_cert to the CA certificate for your server or a certificate bundle containing your CA certification.
You may also set :ssl_verify_mode to 0 to completely disable SSL certificate checks, but this is not recommended.
RubyGems 1.8.10 contains a security fix that prevents malicious gems from executing code when their specification is loaded. See github.com/rubygems/rubygems/pull/165 for details.
This release focused on properly encapsulating functionality. Most of this work focused on moving functionality out of Gem::SourceIndex and Gem::GemPathSearcher into Gem::Specification where it belongs.
After installing RubyGems 1.8.0 you will see deprecations when loading your exsting gems. Run `gem pristine —all —no-extensions` to regenerate your gem specifications safely.
Currently RubyGems does not save the build arguments used to build gems with extensions. You will need to run `gem pristine gem_with_extension —