[1667] in Kerberos-V5-bugs
Returned mail: User unknown
daemon@ATHENA.MIT.EDU (Mail Delivery Subsystem)
Thu Oct 12 20:55:56 1995
Date: Thu, 12 Oct 1995 20:24:42 -0400
From: Mail Delivery Subsystem <MAILER-DAEMON@MIT.EDU>
To: hartmans@MIT.EDU
Resent-To: krb5-bugs@MIT.EDU
Resent-From: Sam Hartman <hartmans@MIT.EDU>
This is a MIME-encapsulated message
--UAA13656.813543882/tertius.mit.edu
The original message was received at Thu, 12 Oct 1995 20:24:33 -0400
from hartmans@localhost
----- The following addresses had delivery problems -----
<krb5-bug@MIT.EDU> (unrecoverable error)
----- Transcript of session follows -----
... while talking to pacific-carrier-annex.mit.edu.:
>>> RCPT To:<krb5-bug@MIT.EDU>
<<< 550 <krb5-bug@MIT.EDU>... User unknown
550 <krb5-bug@MIT.EDU>... User unknown
----- Original message follows -----
--UAA13656.813543882/tertius.mit.edu
Content-Type: message/rfc822
Return-Path: hartmans
Received: (from hartmans@localhost) by tertius.mit.edu (8.6.12/8.6.9) id UAA12628; Thu, 12 Oct 1995 20:24:33 -0400
Message-Id: <199510130024.UAA12628@tertius.mit.edu>
To: "Doug Engert" <DEEngert@anl.gov>
cc: <hartmans@MIT.EDU>, <eichin@cygnus.com>, <krb5-bug@MIT.EDU>
Subject: Re: Krb4 routines using the Krb5 config files
In-reply-to: Your message of "Thu, 12 Oct 1995 11:18:02 CDT."
<9510121618.AA24678@MIT.EDU>
Date: Thu, 12 Oct 1995 20:24:33 EDT
From: Sam Hartman <hartmans>
>>>>> "Doug" == Doug Engert <DEEngert@anl.gov> writes:
Doug> Sam Hartman wrote:
>> Mark Eichin asked me to include a feature request with this
>> followup to my bug report for the following behavior: * the
>> krb4 libs distributed with krb5 should, ideally, use a v5srvtab
>> and v5configuration files to get their configuration info and
>> keys.
Doug> I would strongly disagree. We have been taking advantage of
Doug> the fact that there are two seperate configuration files. We
Doug> have a K4 realm which is using our AFS Kaservers as the
Doug> KDCS, and we also have a K5 realm using our DCE security
Doug> serves as the K5 KDCs.
In this situation, I would argue that you should configure
--with-krb4=some_directory and install a real krb4 package in that
directory. The purpose of including krb4 libraries in the v5 source
tree is to ease upgrading from v4 to v5, and where possible (and I
realize it isn't possible for you), using a single configuration/key
file would be useful.
Unfortunately, maintaining the ability to compile against a
user-supplied libkrb.a does sort of defeat the idea of moving compat_*
int the v4 code.
--Sam
--UAA13656.813543882/tertius.mit.edu--
