How to get shlib version number?

From: Nikola Milutinovic (Nikola.Milutinovic_at_ev.co.yu)
Date: 11/24/05

  • Next message: Nikola Milutinovic: "SUMMARY: How to get shlib version number? (SOLVED)"
    Date: Thu, 24 Nov 2005 15:11:33 +0100
    To: Tru64 Unix Managers <tru64-unix-managers@ornl.gov>
    
    

    Hi all.

    I must say I'm a bit puzzled with this one. This is my problem. I'm
    building OpenSSL 0.9.8a on Tru64 UNIX 4.0D. I'm using native CC and GNU
    Make. Everything builds fine, haven't run test, yet, because I noticed
    one pecauliarity. When I listed dynamic libraries linket into "openssl"
    binary, this is what I got:

    Legba:/home/r/root/build/openssl-0.9.8a# odump -Dl apps/openssl

                            ***LIBRARY LIST SECTION***
            Name Time-Stamp CheckSum Flags Version
    apps/openssl:
            libssl.so Nov 24 14:24:18 2005 0xdf8c8e84 0 0.9.8"
            libcrypto.so Nov 24 14:24:14 2005 0x3f2adb08 0 0.9.8"
            libpthread.so Jun 25 21:19:35 2001 0xb751ba06 0 osf.1
            libmach.so Dec 30 00:16:41 1997 0xe151181d 0 osf.1
            libexc.so Jun 26 23:06:59 1998 0xbf6e7df3 0 osf.1
            libc.so Jun 25 21:14:05 2001 0x5cbd50dd 0 osf.1

    Notice that the version of the OpenSSL libraries is 0.9.8". The
    quotation mark at the end is what puzzles me. It would appear that
    "libssl.so" and "libcrypto.so" were built with that string for version.
    I have verified that "openssl" utility works with these libraries, so no
    mistake there (and there couldn't be any, since linker writes it). I
    could live with it, I guess, but I hate it when something is (is it?)
    obviously out of place.

    Can someone shed some light on this?

    How can I inspect the version written in the library file itself?

    Nix.


  • Next message: Nikola Milutinovic: "SUMMARY: How to get shlib version number? (SOLVED)"

    Relevant Pages

    • Re: On Open Source
      ... > make it possible to revoke either of the certificates ... You could just as easily delete the public key from your other box. ... > up using OpenSSL in a completely insecure way. ... > libraries instead of developing an application specific cryptographic ...
      (sci.crypt)
    • Re: Apache, mod_ssl and openssl?
      ... One way to find out is to temporarily hide the shared OpenSSL libraries ... it's using the shared libraries. ... recompile your apache and life should be ...
      (comp.os.linux.security)
    • Re: On Open Source
      ... > you could just as easily delete the public key from your other box (e.g. ... If OpenSSL only allowed 1 type ... >> be implemented by cryptographers. ... that isn't a reason to say "stop using open source libraries!". ...
      (sci.crypt)
    • Re: Adding standalone RSA code
      ... Mark Murray said: ... when it comes to crypto libraries I'd ... rather stick with OpenSSL. ... however, as stated above, it has quite a few more eyes on it as well. ...
      (freebsd-arch)
    • [CLA-2003:625] Conectiva Security Announcement - openssl
      ... SUMMARY: OpenSSL library vulnerabilities ... against OpenSSL and derived libraries. ... It is recommended that all users upgrade their openssl packages. ... Detailed instructions reagarding the use of apt and upgrade examples ...
      (Bugtraq)