Skip Menu |
Ticket metadata
The Basics
Id: 1222
Status: resolved
Priority: 0/
Queue: OpenSSL-Bugs

Custom Fields
Milestone: (no value)
Subsystem: (no value)
Severity: (no value)
Broken in: (no value)

Owner: Nobody in particular
Requestors: Christoph Martin

More about the requestors

Christoph Martin

Comments about this user: No comment entered about this user
Groups this user belongs to
  • Unprivileged
  • Everyone

New reminder:

Created: Mon Oct 17 09:55:48 2005
Starts: Not set
Started: Tue Dec 15 21:11:15 2015
Last Contact: Tue Dec 15 21:11:15 2015
Due: Mon Oct 17 09:55:48 2005
Closed: Tue Dec 15 21:11:15 2015
Updated: Tue Dec 15 21:11:15 2015 by Matt Caswell

Date: Sat, 15 Oct 2005 00:37:11 +0200
From: Christoph Martin <>
Subject: Please introduce versioned symbols
Download (untitled) / with headers
text/plain 844b

Please introduce versioned symbols in openssl, so that programs linked
to different libraries which in turn are linked to different versions of
openssl will not break. The transition from version 0.9.7 to 0.9.8
without versioned symbols is really a pain otherwise. I sent a proposal
to Please use the tag OPENSSL_0.9.8 etc.

See the discussions in Debian: ff

Christoph Martin, EDV der Verwaltung, Uni-Mainz, Germany
Internet-Mail: Christoph.Martin@Uni-Mainz.DE
Telefon: +49-6131-3926337
Download signature.asc
application/pgp-signature 256b

Message body not shown because it is not plain text.

Date: Mon, 17 Oct 2005 14:12:31 +0200 (CEST)
Subject: Re: [ #1222] Please introduce versioned symbols
From: Richard Levitte - VMS Whacker <>
Download (untitled) / with headers
text/plain 1.8k
[Additional note to get the proposal itself into this ticket's history]

From: Christoph Martin <>
Date: Thu, 13 Oct 2005 23:24:58 +0200
Subject: Proposal for symbol versioning of openssl

Hi folks,

openssl has evolved to a very important library in Linux distribution. A
lot of cryptographic applications link to it including system libraries
like pam modules and apache modules. Now it becomes more and more
difficult to get all the binaries and libraries to link to the same
version of openssl. This leads to situations where an application uses
some libraries where on links to openssl 0.9.7 and another one to
version 0.9.8. Since the symbols of the libraries are not yet versioned
this leads to severe segfaults.

For the Debian project we want to introduce symbol versioning like it is
done not only in glibc. Since we want to maintain binary compatibility
with as much other distributions we want to coordinate this work with
you. At this time I only have contact addresses to a few maintainers.

We propose that we version all exported symbols for openssl 0.9.8 with
with the label OPENSSL_0.9.8, like glibc has the label GLIBC_2.0 etc.
For that to happen I introduced a version script openssl.ld with the
following contents:

OPENSSL_0.9.8 {

It has to be in the toplevel directory and in the engines directory.

The SHARED_LDFLAGS get the additional options

I will come with a proper patch soon.

Please lets discuss this proposal and some detailed questions.

What do you think of it? Would you include this change in you
distribution? Does upstream include it too?

Is it ok to tag all (*) symbols with this version or should there be a
more complex version script?

What about symbol versioning of openssl 0.9.7? (Debian includes both
versions for compatibility reasons in the current unstable distro.)

This feature is now available in master (1.1.0). Closing this ticket.