[21944] in Kerberos

home help back first fref pref prev next nref lref last post

Re: kerberos binary compatiblity

daemon@ATHENA.MIT.EDU (Sam Hartman)
Wed Jul 7 15:28:00 2004

To: "Nebergall, Christopher" <cneberg@sandia.gov>
From: Sam Hartman <hartmans@mit.edu>
Date: Wed, 07 Jul 2004 15:26:00 -0400
In-Reply-To: <16F54D8E44BBEE4BBBDB5EFB3AEEB86D0102EEC8@es06snlnt.sandia.gov>
	(Christopher Nebergall's message of "Wed, 7 Jul 2004 09:33:57 -0600")
Message-ID: <tslr7rn8vqv.fsf@cz.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: "'kerberos@mit.edu'" <kerberos@mit.edu>
Errors-To: kerberos-bounces@mit.edu

As a general rule, MIT Kerberos releases have not broken ABI
compatibility in a long time.  We believe programs compiled against
MIT Kerberos 1.2.0 should still work against MIT Kerberos 1.3.4.

The problem you seem to be running into is that Redhat has not chosen
to keep ABI compatibility between their 1.2.x-based and 1.3.x-based
versions of MIT Kerberos.  They seem to have changed how they handle
libcom_err and not included a compatibility shim for the libcom_err
they dropped.  I think they may be taking advantage of an option in
Kerberos 1.3.x to use the system com_err library.

Unfortunately, by choosing to use that option and by not providing a
compatibility shim, they have broken their ABI.  There is nothing that
MIT can do to help with this.  I suggest trying to work out a solution
with Redhat.


Kerberos mailing list           Kerberos@mit.edu

home help back first fref pref prev next nref lref last post