From: Jim Weirich <jim@...>
Date: 2005-09-07T13:04:06+09:00
Subject: Re: SSL and gems -- was Re: Rake 0.6.0 Released

On Tuesday 06 September 2005 11:39 pm, Joel VanderWerf wrote:
> Jim Weirich wrote:
> > Yeah, its the fact that the gem is signed and RubyGems is insisting on
> > having SSL available.  I think it should only do that if the security
> > policy requires it, but that's a gems issue that needs looking into.
> >
> > So, what to do?
> >
> > (1) If you thought you had SSL, and you don't, then you probably should
> > look into that.
>
> That's it. My openssl.so was not installed correctly. It built ok in
> ext/openssl, but I had to disable the RUBYOPT=rubygems for it to install
> (and then gem update was able to install rake-0.6.0). With
> RUBYOPT=rubygems, I was getting this:
>
> $ make install
> /usr/local/lib/ruby/site_ruby/1.8/rubygems/security.rb:18: uninitialized
> constant OpenSSL::Digest::SHA1 (NameError)
>         from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:397:in `require'
>         from /usr/local/lib/ruby/site_ruby/1.8/rubygems.rb:397
>         from /usr/local/lib/ruby/site_ruby/1.8/ubygems.rb:4:in `require'
>         from /usr/local/lib/ruby/site_ruby/1.8/ubygems.rb:4
> make: *** [/usr/local/lib/ruby/site_ruby/1.8/i686-linux/openssl.so] Error 1

Thanks for the feedback.  RubyGems assumes that if you can successfully 
require the openssl library, then ssl is available.  Unfortunately, in the 
half installed state you were in, the openssl.so library was available but 
not the ruby portion (openssl.rb).  So the require succeeded, fooling 
RubyGems into thinking the entire ssl infrastructure was in place when it was 
not.

I'll put a fix in for that.

-- 
-- Jim Weirich    jim@weirichhouse.org     http://onestepback.org
-----------------------------------------------------------------
"Beware of bugs in the above code; I have only proved it correct, 
not tried it." -- Donald Knuth (in a memo to Peter van Emde Boas)