[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20041107134115.GB1056@openwall.com>
Date: Sun, 7 Nov 2004 16:41:15 +0300
From: Solar Designer <solar@...nwall.com>
To: owl-users@...ts.openwall.com
Subject: Re: Owl-current moved to glibc 2.3.x
On Sun, Nov 07, 2004 at 04:22:43AM +0100, Maciek Pasternacki wrote:
> On Boomtime, The Aftermath 20, 3170 YOLD, Solar Designer wrote:
> > As for technical problems, the only significant one is with Perl. I
> > know that people have Owl 1.1 installs with many custom Perl modules
> > built ...
> There may be also problems with openssl -- binaries linked with it
> require exact version of libssl.so and libcrypto.so, and openssl was
> also upgraded in last -current.
You've lost context here. We were talking about possibly rolling
updates from Owl-current _prior_ to the Big Update into 1.1-stable.
That still used the old OpenSSL.
As for the latest -current, yes, we've broken binary compatibility for
OpenSSL, and we've also dropped support for libdb.so.2 and libdb.so.3.
These are now binary-compatible with newer systems (such as RHL9), but
not with older Owl. So those who have built/linked custom software
against old OpenSSL and/or old libdb on Owl 1.1, will have to rebuild
that when upgrading to the newest Owl-current.
--
Alexander Peslyak <solar at openwall.com>
GPG key ID: B35D3598 fp: 6429 0D7E F130 C13E C929 6447 73C3 A290 B35D 3598
http://www.openwall.com - bringing security into open computing environments
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
