[900] in Kerberos_V5_Development
Re: "Two copies of DES library" change breaks K5 compat w/Cygnus K4
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Mon Mar 20 11:19:04 1995
From: "Jonathan I. Kamens" <jik@cam.ov.com>
Date: Mon, 20 Mar 1995 11:22:19 -0500
To: John Gilmore <gnu@cygnus.com>
Cc: "Theodore Ts'o" <tytso@MIT.EDU>, gnu@cygnus.com, krbdev@MIT.EDU,
gnu@cygnus.com
In-Reply-To: [898]
[0898] daemon@ATHENA.MIT.EDU (John Gilmore) Kerberos_V5_Development 03/19/95 21:13 (32 lines)
Date: Sun, 19 Mar 1995 18:13:12 -0800
From: John Gilmore <gnu@cygnus.com>
I *don't* recommend adding that to your lib425. What I recommend is
not trying to break an interface in half and substitute for half of it.
It's only broken for Cygnus. It works fine in the MIT code base.
If you bring in any piece of krb4, bring the whole thing in. Saving
40K (or 400K) when built for V4-compatability is simply not a big deal.
Human time is what this project is really short on. Disk space and RAM
we have gobs of. Let's stop wasting our time on this.
By requiring libdes.a for anyone who wants to use V4-compatibility,
you are wasting *their* time, because then they have to compile two
functionally equivalent DES libraries in order to build V5. Not to
mention that the V4 DES code is not exactly the most portable, whereas
the krb5b4pl3 DES implementation is better and more portable than
anything that's been used previously.
I suggest you add the function that is missing at your site into your
site's libdes425.a. Either that, or take it out of the version of
libkrb.a that you're using with V5 at your site. Either that, or if
it really provides useful functionality that V5 should be using too,
then implement an equivalent function for V5 and submit it to be
included in the V5 libraries to that the 425 libraries can map to it.
jik
