[22699] in Kerberos
RE: Kerberos AFS ticket problem
daemon@ATHENA.MIT.EDU (Kevin Coffman)
Wed Oct 20 13:19:51 2004
From: "Kevin Coffman" <kwc@citi.umich.edu>
To: "'Derek Harkness'" <dharknes@umd.umich.edu>
Date: Wed, 20 Oct 2004 12:25:24 -0400
Message-ID: <008201c4b6c1$670ec0e0$6400000a@citi.umich.edu>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
In-Reply-To: <D4DC62E6-229F-11D9-BC6F-000A95CA1654@umd.umich.edu>
Content-Transfer-Encoding: 8bit
cc: kerberos@mit.edu
Reply-To: kwc@citi.umich.edu
Errors-To: kerberos-bounces@mit.edu
Hi Derek,
I have a few questions, and then I can generate a new keytab for your
afs/umd.umich.edu principal. You will then need to run the asetkey program
to copy the key out of the keytab and into your KeyFile. You'll need a copy
of the asetkey program, hence the questions:
1) What OS platform are you running your OpenAFS server(s) on?
2) Are you using Transarc paths or the OpenAFS default paths?
(is your KeyFile in /usr/afs/etc/ or /usr/local/etc/openafs/server/?)
After I create the new keytab, clients that are already using the old key
should continue to work. Clients getting tickets from
kerberos-[124].umich.edu will not work until you add the new key to your
KeyFile and propagate that to all your servers.
K.C.
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
