[3228] in Kerberos
Sun V4 KNFS living in a V5 world?
daemon@ATHENA.MIT.EDU (Jeff Bacon)
Wed May 4 11:00:49 1994
To: kerberos@MIT.EDU
Date: 2 May 1994 17:13:43 -0400
From: bacon@mtu.edu (Jeff Bacon)
Theodore Ts'o (tytso@MIT.EDU) wrote:
: V5 KDC is set up to listen on two ports kerberos (88) and kerberos-sec
: (750), and the V4 compatibility option is turned on, if it sees a V4
: request on either port, it will process it using the V5 database and
: return a V4 response to the client.
as a followon to this topic:
is anyone out there using sun's kerberized NFS code with a V5 server?
The problem: sun-krb-nfs rather insists on having V4 tickets in a
(presumably v4-standard) /tmp/tkt file and a V4 srvtab. All wonderful
and good, I can provide all that...but if I'm running V5
rlogin/telnet/ftp/etc, those are all going to want V5 tickets.
which means:
a) Joe User is going to have to run kinit twice, once for v4, once
for v5 (UGH)
b) v5 kinit is gonna have to write two cache files, one with the v4 tickets,
one with the v5 tickets
c) I rewrite everything (yeah right)
the first logical obvious solution is to hack the v5 kinit.c to
simply call /usr/bin/kinit (sun's v4 version) and hand it the
password it collected from the command line. ugly, but effective.
is there another logical, obvious solution I'm missing here?
-bacon
--
= Jeff Bacon General Systems Hack, Michigan Technological Univ. =
= bacon@mtu.edu ph-(906)487-2197 fax-(906)487-2782 DoD#2110 I'm the NRA =
= John 3:16 isn't chapter and verse, it's a way of life =
