>-----Original Message-----
>From: Joe Orton [mailto:[EMAIL PROTECTED]]
>Sent: 07 September 2001 15:09
>To: Robert Pungello
>Cc: [EMAIL PROTECTED]
>Subject: Re: libssl.so & libcrypto.so, again.
>
>
>On Fri, Sep 07, 2001 at 08:09:06AM -0400, Robert Pungello wrote:
>> Hello All. I know there have been a few questions about
>this already, but
>> I'm still a bit confused. I'm using Red Hat 7.1 with the
>openssl-0.9.6-3
>> and openssl-devel-0.9.6-3 packages installed. In addition,
>I have also
>> installed openssl-0.9.6b myself because at the time I didn't
>realize the
>> previously installed package existed. When I look in my /usr/lib/
>> directory, I see the following files (among others):
>> libssl.a, libssl.so, libssl.so.0.9.6, libssl.so.1
>> libcrypto.a, libcrypto.so, libcrypto.so.0.9.6, libcrypto.so.1.
>
>Okay, I'll try my best at answering this... with RHL7.1, you would get
>the following: (the same applies throughout for libssl as libcrypto)
>
>libcrypto.so.0.9.6: the actual shared library
>libcrypto.so.1: symlink to above
>
>If you have upgraded your system from 7.0, you will also have
>
>libcrypto.so.0.9.5a: another real actual shared library
>libcrypto.so.0: symlink to above
>
>These symlinks are created by the 'ldconfig' command (run automagically
>just after the RPMs are installed).
>
>Each time that the ABI changes (so that the library is no longer
>backwards-compatible), and a new RPM is made, you'll see a new symlink
>libcrypto.so.N (where N increases by 1 each time). This allows Red Hat
>to keep backwards compatibility with old applications. So in the next
>release, if you upgrade, IIRC you'll find:
>
>libcrypto.so.0.9.6a: a real library
>libcrypto.so.2: symlink to above
>
>and if 0.9.7 isn't binary compatibility with 0.9.6a, then at some point
>later you'll find an RPM with:
>
>libcrypto.so.0.9.7: real shared library
>libcrypto.so.3: symlink to above
>
>I hope this makes sense so far. The -devel package will install the
>following two libs, which you only need if you want to build any
>packages which link against OpenSSL:
>
>libcrypto.so: symlink to real library again
>libcrypto.a: the static library
>
>So that's how Red Hat's OpenSSL RPMs work, I think. This differs
>slightly from how the stock OpenSSL tarballs will install shared
>libraries, since the stock Makefiles don't try to cope with binary
>compatibility issues. I think if you install a stock OpenSSL
>over a RHL
>system, it will create
>
>libcrypto.so.X.Y.Z
>libcrypto.so, libcrypto.so.0: symlinks to above
>
>This will be a problem if you have any applications on your system
>linked against the 0.9.5a library if you upgraded from RHL 7.0, but
>otherwise, your existing applications should work fine still.
>
>Compiling things on this system will probably be okay, unless you ever
>upgrade any of the OpenSSL RPMs, in which case your applications may
>break again, I'm not sure. I'd advise doing
I have tried upgrading the version of openssl 0.9.6 on a RedHat 7.1 machine
to 0.9.6b using the RedHat openssl.spec file and it broke several
applications, including openssh. This is why I've been saying in the case of
RedHat 7.x to stick with the RedHat openssl packages. Now if you could just
provide different packages for us Brits (and others) who aren't restricted
by RC5 and IDEA patents...
>
># rpm --erase openssl-devel
># rpm -Uvh openssl-devel-0.9.6-3.rpm ### from the CD, or wherever
>
>if you wish to get back under the RPM management. You may need
>a --force
>too.
>
>Hope some of that makes sense :)
>
>joe
It makes sense to me. It's good to see someone from RedHat giving a hand
with this one, as it does come up often on the list.
-
John Airey
Internet systems support officer, ITCSD, Royal National Institute for the
Blind,
Bakewell Road, Peterborough PE2 6XU,
Tel.: +44 (0) 1733 375299 Fax: +44 (0) 1733 370848 [EMAIL PROTECTED]
-
NOTICE: The information contained in this email and any attachments is
confidential and may be legally privileged. If you are not the
intended recipient you are hereby notified that you must not use,
disclose, distribute, copy, print or rely on this email's content. If
you are not the intended recipient, please notify the sender
immediately and then delete the email and any attachments from your
system.
RNIB has made strenuous efforts to ensure that emails and any
attachments generated by its staff are free from viruses. However, it
cannot accept any responsibility for any viruses which are
transmitted. We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent those of RNIB.
RNIB Registered Charity Number: 226227
Website: http://www.rnib.org.uk
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
