Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 Mar 1998 06:40:01 -0800 (PST)
From:      Robert Watson <robert@cyrus.watson.org>
To:        freebsd-bugs
Subject:   Re: bin/5999: kadmin bug -- crypt not linked correctly, fails to work 
Message-ID:  <199803141440.GAA12675@hub.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/5999; it has been noted by GNATS.

From: Robert Watson <robert@cyrus.watson.org>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: bin/5999: kadmin bug -- crypt not linked correctly, fails to work 
Date: Sat, 14 Mar 1998 09:35:20 -0500 (EST)

 On Sat, 14 Mar 1998, Jordan K. Hubbard wrote:
 
 > > Using the KTH Kerberos4 recently added to FreeBSD.  KERBEROS4 defined in
 > > /etc/make.conf.  Many machines.
 > 
 > Known problem and several anguished emails to Mark Murray are
 > outstanding without reply.  If I don't hear something back from him by
 > Wednesday and no one else has an obvious fix, I'll back all of the K4
 > changes out of -stable.  Due to a name change in make.conf, this was
 > mistakenly not caught until fairly recently or I'd have dealt with it
 > even before code freeze.
 
 Jordan,
 
 I believe I attached a patch to the email; it appears to work correctly
 here, as it just adds a -lcrypt to the kadmin Makefile.  When you say back
 out the K4 changes, do you mean pull out on the KTH upgrade for 2.2.6?  A
 better course of action would probably be to fix the Makefile.  A number
 of libraries and include files have changed in KTH, and are now in fact in
 a *standard* place unlike previous versions of FreeBSD :).  So many more
 things compile cleanly under KTH that it seems extremely worthwhile. :)
 The old Kerberos was also quite broken for multi-homed hosts due to a bug
 in the kerberos client libraries.  I believe the new libraries actually
 function correctly in that environment, which is quite a plus :).  Putting
 in -lcrypt seems a reasonable fix; it certainly breaks nothing, regardless
 of the code freeze.  Of course, you have no doubt heard *that* one before.
 
   Robert N Watson 
 
 Carnegie Mellon University http://www.cmu.edu/
 SafePort Network Services  http://www.safeport.com/
 robert@fledge.watson.org   http://www.watson.org/~robert/
 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803141440.GAA12675>