[966] in arla-drinkers
Re: Arla and Heimdal?
daemon@ATHENA.MIT.EDU (Jeffrey Hutzelman)
Mon Jul 12 02:42:04 1999
From owner-arla-drinkers@stacken.kth.se Mon Jul 12 06:42:02 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 25193 invoked from network); 12 Jul 1999 06:42:01 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 12 Jul 1999 06:42:01 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id IAA08299
for arla-drinkers-list; Mon, 12 Jul 1999 08:35:21 +0200 (MET DST)
Received: from dhcp29172.ietf.uninett.no (dhcp31162.ietf.uninett.no [128.39.31.162])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id IAA08295
for <arla-drinkers@stacken.kth.se>; Mon, 12 Jul 1999 08:35:16 +0200 (MET DST)
Received: (from assar@localhost) by dhcp29172.ietf.uninett.no (8.9.3/8.7.3) id IAA03873; Mon, 12 Jul 1999 08:35:37 +0200 (CEST)
Date: Wed, 07 Jul 1999 17:48:22 -0400
From: Jeffrey Hutzelman <jhutz+@cmu.edu>
To: bam@snoopy.apana.org.au, Assar Westerlund <assar@sics.se>
cc: heimdal-discuss@sics.se, arla-drinkers@stacken.kth.se
Subject: Re: Arla and Heimdal?
Message-ID: <3656766334.931369702@AFSTEST-2.FAC.CS.CMU.EDU>
In-Reply-To: <19990707090425.B15483@snoopy.apana.org.au>
Originator-Info: login-token=Mulberry:01C2sOonXTgxZXto0lUO1/BJbQes9N5JaBmXEVC9mKKwvedBM=;
token_authority=postmaster@andrew.cmu.edu
X-Mailer: Mulberry (Win32) [1.4.1, s/n S-100002]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Approved: hund
Lines: 20
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
On Wednesday, July 07, 1999, 9:04 AM +1000 Brian May
<bam@snoopy.apana.org.au> wrote:
> So, for krb5 support, I guess the only think required is to write
> code for the hooks in the rxkad module...
Unfortunately, it's somewhat more complicated that that, due to a
combination of the need to maintain backwards compatibility with non-krb5
rxkad implementations (otherwise, you wouldn't be able to talk to servers
in a non-krb5 cell) and various other factors. The "hooks" that appear to
be present in rxkad are simply not enough.
-- Jeffrey T. Hutzelman (N3NHS) <jhutz+@cmu.edu>
Sr. Research Systems Programmer
School of Computer Science - Research Computing Facility
Carnegie Mellon University - Pittsburgh, PA
