[14629] in Kerberos
Re: How to configure a Kerberos 5 Linux client of a Solaris KDC server
daemon@ATHENA.MIT.EDU (K.J.Richardson@gre.ac.uk)
Fri Jul 6 04:28:56 2001
Date: Fri, 6 Jul 2001 09:24:51 +0100 (BST)
From: <K.J.Richardson@gre.ac.uk>
To: "Booker C. Bense" <bbense@networking.stanford.edu>
cc: kerberos@mit.edu
In-Reply-To: <Pine.GSO.4.33.0107050729020.6419-100000@shred.stanford.edu>
Message-ID: <Pine.GSO.3.92.1010706092236.2622C-100000@whack>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Booker,
Thanks for the reply.
So given that we want to support Linux clients, does that mean that we
should install MIT Kerberos on the Suns in preference to SEAM, or would
there be problems with that too?
Thanks,
Kevin
-------------------------------------------------------------------------------
Dr Kevin J. Richardson, | K.J.Richardson@greenwich.ac.uk
Computing Services, | tel +44 (0)20 8331 8392
University of Greenwich, | fax +44 (0)20 8331 8385
Wellington St., London SE18 6PF |
-------------------------------------------------------------------------------
On Thu, 5 Jul 2001, Booker C. Bense wrote:
> On Wed, 4 Jul 2001 rk21@gre.ac.uk wrote:
>
> > I am having trouble installing a PC running Red HAT 7.1 as a Kerberos 5
> > client of a Sun KDC server running Solaris 8 and SEAM 1.01 (Sun
> > implementation of Kerberos 5).
> >
> > I have successfully set up a Solaris 8 Kerberos 5 client. However when I
> > try to set up the PC client (on which krb-workstation and krb5-libs have
> > been installed) I cannot get into kadmin on the client. It recognises the
> > password correctly but I get the error message
> >
> >
>
> - SEAM uses a different admin protocol than the kadmin that comes with
> MIT. In practice this means that it's very difficult to use a SEAM KDC
> with anything but SEAM clients. Extremely stupid on SUN's part, they
> don't even given you an API to write your own admin client.
>
> - Booker C. Bense
>
>
