Rubyinstaller devel - Nov 2008 - Use openssl 0.9.8e in the next version?

Hi,

I''m testing your RC1 and using it for rails 2.1 and postgresql.
It turnout your libeay32.dll and ssleay32.dll conflict with
PostgreSQL 8.3.1 version of the same dll (0.9.8.4 vs 0.9.8.5).

Could you upgrade the next version to use OpenSSL 0.9.8e like PostgreSQL?

I''m choosing that particular version of PostgreSQL because that the
version
the target server will use (Ubuntu LTS 8.04).

Thanks,


-- Zakaria
   z4k4ri4 at gmail.com             Yahoo!: z4k4ri4

I wonder if there''s a way to use separate versions of the
dll''s
without causing conflicts.
-=R

On Mon, Nov 17, 2008 at 11:28 PM, Zakaria <z4k4ri4 at gmail.com>
wrote:
> Hi,
>
> I''m testing your RC1 and using it for rails 2.1 and postgresql.
> It turnout your libeay32.dll and ssleay32.dll conflict with
> PostgreSQL 8.3.1 version of the same dll (0.9.8.4 vs 0.9.8.5).
>
> Could you upgrade the next version to use OpenSSL 0.9.8e like PostgreSQL?
>
> I''m choosing that particular version of PostgreSQL because that
the version
> the target server will use (Ubuntu LTS 8.04).
>
> Thanks,
>
>
> -- Zakaria
>   z4k4ri4 at gmail.com             Yahoo!: z4k4ri4
> _______________________________________________
> Rubyinstaller-devel mailing list
> Rubyinstaller-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubyinstaller-devel
>

On Tue, Nov 18, 2008 at 4:28 AM, Zakaria <z4k4ri4 at gmail.com>
wrote:
> Hi,
>
> I''m testing your RC1 and using it for rails 2.1 and postgresql.
> It turnout your libeay32.dll and ssleay32.dll conflict with
> PostgreSQL 8.3.1 version of the same dll (0.9.8.4 vs 0.9.8.5).
>
> Could you upgrade the next version to use OpenSSL 0.9.8e like PostgreSQL?
>
We can try, but I found problems between the openssl extension bundled
with the Ruby version we are using and newer OpenSSL releases.

Did you tried replacing those files for the newer ones?

Just rename the ones in Ruby/bin to .old or something and copy over
the ones from PostgreSQL
> I''m choosing that particular version of PostgreSQL because that
the version
> the target server will use (Ubuntu LTS 8.04).
>
> Thanks,
>
>
> -- Zakaria
>   z4k4ri4 at gmail.com             Yahoo!: z4k4ri4
-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

On Tue, Nov 18, 2008 at 1:11 PM, Roger Pack <rogerpack2005 at gmail.com>
wrote:
> I wonder if there''s a way to use separate versions of the
dll''s
> without causing conflicts.
> -=R
>
The only way to avoid that is do static linked version of all the
dependencies Ruby depends on (like zlib, openssl, readline and
others).

-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

On Tue, Nov 18, 2008 at 4:28 AM, Zakaria <z4k4ri4 at gmail.com>
wrote:
> Hi,
>
> I''m testing your RC1 and using it for rails 2.1 and postgresql.
> It turnout your libeay32.dll and ssleay32.dll conflict with
> PostgreSQL 8.3.1 version of the same dll (0.9.8.4 vs 0.9.8.5).
>
> Could you upgrade the next version to use OpenSSL 0.9.8e like PostgreSQL?
>
> I''m choosing that particular version of PostgreSQL because that
the version
> the target server will use (Ubuntu LTS 8.04).
>
After futher review, it seems sseay32.dll and libeay32.dll "official"
builds are prepared with VC9,

http://www.slproweb.com/products/Win32OpenSSL.html

That will render the updated files incompatible with current One-Click
installer (VC6).

Too bad there isn''t other releases of this for MinGW or VC6 compilers.

The alternative will be manually copy these files into Ruby/bin once installed.

MinGW version of One-Click will not be affected by this.

Regards,
-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

I''m sorry I did not get back to you immediately.
Real-Life(tm) take me and make me forget about this question.

On Tue, Nov 18, 2008 at 10:13 PM, Luis Lavena <luislavena at gmail.com>
wrote:
> On Tue, Nov 18, 2008 at 4:28 AM, Zakaria <z4k4ri4 at gmail.com>
wrote:
>> Hi,
>> I''m testing your RC1 and using it for rails 2.1 and
postgresql.
>> It turnout your libeay32.dll and ssleay32.dll conflict with
>> PostgreSQL 8.3.1 version of the same dll (0.9.8.4 vs 0.9.8.5).
>> Could you upgrade the next version to use OpenSSL 0.9.8e like
PostgreSQL?
> We can try, but I found problems between the openssl extension bundled
> with the Ruby version we are using and newer OpenSSL releases.
> Did you tried replacing those files for the newer ones?
> Just rename the ones in Ruby/bin to .old or something and copy over
> the ones from PostgreSQL
Yes, I try and it seem all right.
Is there any test script that I can try to verified that my ruby
openssl is not affected?
BTW, what is your plan for OCI? When can we expect another RC?
> --
> Luis Lavena
> AREA 17
-- Zakaria
   z4k4ri4 at gmail.com             Yahoo!: z4k4ri4
   http://pemula.linux.or.id
   Mau invite gmail? japri aja.

On Thu, Dec 4, 2008 at 10:27 PM, Zakaria <z4k4ri4 at gmail.com>
wrote:
> I''m sorry I did not get back to you immediately.
> Real-Life(tm) take me and make me forget about this question.
>
I know about that :-P
> On Tue, Nov 18, 2008 at 10:13 PM, Luis Lavena <luislavena at
gmail.com> wrote:
>> On Tue, Nov 18, 2008 at 4:28 AM, Zakaria <z4k4ri4 at gmail.com>
wrote:
>>> Hi,
>
>>> I''m testing your RC1 and using it for rails 2.1 and
postgresql.
>>> It turnout your libeay32.dll and ssleay32.dll conflict with
>>> PostgreSQL 8.3.1 version of the same dll (0.9.8.4 vs 0.9.8.5).
>
>>> Could you upgrade the next version to use OpenSSL 0.9.8e like
PostgreSQL?
>
>> We can try, but I found problems between the openssl extension bundled
>> with the Ruby version we are using and newer OpenSSL releases.
>
>> Did you tried replacing those files for the newer ones?
>
>> Just rename the ones in Ruby/bin to .old or something and copy over
>> the ones from PostgreSQL
>
> Yes, I try and it seem all right.
> Is there any test script that I can try to verified that my ruby
> openssl is not affected?
Hmn, not that I''m aware of, you could try installing mongrel gem which
are signed:

gem install mongrel -P HighSecurity

That uses OpenSSL to verify the signed gem
> BTW, what is your plan for OCI? When can we expect another RC?
>
So far seems there wasn''t new errors with current installer. So
I''ll
work on marking that release as Final and do the announce in
RubyForge.

I''ll love to focus in the new installer to be able to deliver both
1.8.6 and 1.9.1 by Christmas (or a bit after) :-D

-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

On Tue, Nov 18, 2008 at 10:14 PM, Luis Lavena <luislavena at gmail.com>
wrote:
> On Tue, Nov 18, 2008 at 1:11 PM, Roger Pack <rogerpack2005 at
gmail.com> wrote:
>> I wonder if there''s a way to use separate versions of the
dll''s
>> without causing conflicts.
>> -=R
> The only way to avoid that is do static linked version of all the
> dependencies Ruby depends on (like zlib, openssl, readline and
> others).
On my windows box, I install SilkSVN and among the files they install are
SlikSvn-libeay32.dll and SlikSvn-ssleay32.dll. There are just a renamed
version of libeay32.dll and ssleay32.dll.

Maybe you could use those trick too?
> --
> Luis Lavena
> AREA 17
Wassallam,


-- Zakaria
   z4k4ri4 at gmail.com             Yahoo!: z4k4ri4
   http://pemula.linux.or.id
   Mau invite gmail? japri aja.

On Thu, Dec 4, 2008 at 10:36 PM, Zakaria <z4k4ri4 at gmail.com>
wrote:
> On Tue, Nov 18, 2008 at 10:14 PM, Luis Lavena <luislavena at
gmail.com> wrote:
>> On Tue, Nov 18, 2008 at 1:11 PM, Roger Pack <rogerpack2005 at
gmail.com> wrote:
>>> I wonder if there''s a way to use separate versions of the
dll''s
>>> without causing conflicts.
>>> -=R
>
>> The only way to avoid that is do static linked version of all the
>> dependencies Ruby depends on (like zlib, openssl, readline and
>> others).
>
> On my windows box, I install SilkSVN and among the files they install are
> SlikSvn-libeay32.dll and SlikSvn-ssleay32.dll. There are just a renamed
> version of libeay32.dll and ssleay32.dll.
>
> Maybe you could use those trick too?
>
Having a different OpenSSL libraries to link against still requires us
to compile them :-P

Anyway, let see how things end about building those packages.
-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

On Fri, Dec 5, 2008 at 10:35 AM, Luis Lavena <luislavena at gmail.com>
wrote:
> Hmn, not that I''m aware of, you could try installing mongrel gem
which
> are signed:
> gem install mongrel -P HighSecurity
> That uses OpenSSL to verify the signed gem
After doing:
gem cert --add mongrel-public_cert.pem
gem install mongrel -P HighSecurity

they fail with error:
Exception `NameError'' at
C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:134 -
uninitialized constant Gem::Commands::InstallCommand
Exception `Gem::LoadError'' at
C:/Ruby/lib/ruby/site_ruby/1.8/rubygems.rb:636 - Could not find
RubyGem sources (> 0.0.1)

Exception `NoMethodError'' at
C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/security.rb:435 - undefined
method `public_key'' for nil:NilClass
Exception `RuntimeError'' at
C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/package/tar_input.rb:93 -
Couldn''t verify data signature: undefined method `public_key''
for
nil:NilClass
ERROR:  While executing gem ... (RuntimeError)
    Couldn''t verify data signature: undefined method
`public_key'' for
nil:NilClass
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/package/tar_input.rb:93:in
`initialize''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/package/tar_input.rb:18:in
`new''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/package/tar_input.rb:18:in
`open''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/package.rb:56:in `open''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/format.rb:67:in
`from_io''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/format.rb:51:in
`from_file_by_path''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/format.rb:50:in `open''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/format.rb:50:in
`from_file_by_path''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/installer.rb:114:in
`initialize''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:236:in
`new''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:236:in
`install''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:219:in
`each''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/dependency_installer.rb:219:in
`install''
       
C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:86:in
`execute''
       
C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:83:in
`each''
       
C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/commands/install_command.rb:83:in
`execute''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command.rb:136:in
`invoke''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:105:in
`process_args''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:75:in
`run''
        C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/gem_runner.rb:39:in
`run''
        C:/Ruby/bin/gem:24

My gem is 1.3.1
I don''t know whose at fault here.
>> BTW, what is your plan for OCI? When can we expect another RC?
> So far seems there wasn''t new errors with current installer. So
I''ll
> work on marking that release as Final and do the announce in
> RubyForge.
> I''ll love to focus in the new installer to be able to deliver both
> 1.8.6 and 1.9.1 by Christmas (or a bit after) :-D
Looking forward for those
> --
> Luis Lavena
> AREA 17
-- Zakaria
   z4k4ri4 at gmail.com             Yahoo!: z4k4ri4
   http://pemula.linux.or.id
   Mau invite gmail? japri aja.

On Thu, Dec 4, 2008 at 11:03 PM, Zakaria <z4k4ri4 at gmail.com>
wrote:
> On Fri, Dec 5, 2008 at 10:35 AM, Luis Lavena <luislavena at
gmail.com> wrote:
>> Hmn, not that I''m aware of, you could try installing mongrel
gem which
>> are signed:
>
>> gem install mongrel -P HighSecurity
>
>> That uses OpenSSL to verify the signed gem
>
> After doing:
> gem cert --add mongrel-public_cert.pem
> gem install mongrel -P HighSecurity
>
> they fail with error:
> Exception `NameError'' at
> C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:134 -
> uninitialized constant Gem::Commands::InstallCommand
> Exception `Gem::LoadError'' at
> C:/Ruby/lib/ruby/site_ruby/1.8/rubygems.rb:636 - Could not find
> RubyGem sources (> 0.0.1)
>
Hmn, looks like is a old version of RubyGems?

try "gem env" for provide that information to us.
>
> My gem is 1.3.1
> I don''t know whose at fault here.
>
Oh, even more confused now...

RubyGems should no longer look for sources gem, it''s gone since 0.9.5
>>> BTW, what is your plan for OCI? When can we expect another RC?
>
>> So far seems there wasn''t new errors with current installer.
So I''ll
>> work on marking that release as Final and do the announce in
>> RubyForge.
>
>> I''ll love to focus in the new installer to be able to deliver
both
>> 1.8.6 and 1.9.1 by Christmas (or a bit after) :-D
>
> Looking forward for those
>
Me too :-)

-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

On Fri, Dec 5, 2008 at 8:34 PM, Luis Lavena <luislavena at gmail.com>
wrote:
> On Thu, Dec 4, 2008 at 11:03 PM, Zakaria <z4k4ri4 at gmail.com>
wrote:
> > After doing:
> > gem cert --add mongrel-public_cert.pem
> > gem install mongrel -P HighSecurity
> > they fail with error:
> > Exception `NameError'' at
> > C:/Ruby/lib/ruby/site_ruby/1.8/rubygems/command_manager.rb:134 -
> > uninitialized constant Gem::Commands::InstallCommand
> > Exception `Gem::LoadError'' at
> > C:/Ruby/lib/ruby/site_ruby/1.8/rubygems.rb:636 - Could not find
> > RubyGem sources (> 0.0.1)
> Hmn, looks like is a old version of RubyGems?
> try "gem env" for provide that information to us.
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.1
  - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32]
  - INSTALLATION DIRECTORY: C:/Ruby/lib/ruby/gems/1.8
  - RUBY EXECUTABLE: C:/Ruby/bin/ruby.exe
  - EXECUTABLE DIRECTORY: C:/Ruby/bin
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86-mswin32-60
  - GEM PATHS:
     - C:/Ruby/lib/ruby/gems/1.8
     - C:/Documents and Settings/Zakaria/.gem/ruby/1.8
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :benchmark => false
     - :backtrace => false
     - :bulk_threshold => 1000
  - REMOTE SOURCES:
     - http://gems.rubyforge.org/
> --
> Luis Lavena
> AREA 17
-- Zakaria
  z4k4ri4 at gmail.com             Yahoo!: z4k4ri4