[23161] in Kerberos
RE: MIT Kerberos and Solaris 10 Kerberos
daemon@ATHENA.MIT.EDU (Heilke, Rainer)
Tue Jan 11 14:05:46 2005
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Date: Tue, 11 Jan 2005 12:03:02 -0700
Message-ID: <A28A519A6A08AD4A9553A9DB5265FD3E01CE2415@is030.atco.com>
From: "Heilke, Rainer" <Rainer.Heilke@atcoitek.com>
To: "Tom Yu" <tlyu@mit.edu>, "Wyllys Ingersoll" <wyllys.ingersoll@sun.com>
Content-Transfer-Encoding: 8bit
cc: kerberos@mit.edu
Errors-To: kerberos-bounces@mit.edu
Thanks. We'll have to keep our eyes open for 5-1.4.
Rainer
> -----Original Message-----
> From: Tom Yu [mailto:tlyu@mit.edu]
> Sent: Tuesday, January 11, 2005 11:12 AM
> To: Wyllys Ingersoll
> Cc: Heilke, Rainer; kerberos@mit.edu
> Subject: Re: MIT Kerberos and Solaris 10 Kerberos
>
>
> >>>>> "Wyllys" == Wyllys Ingersoll <wyllys.ingersoll@sun.com> writes:
>
> Wyllys> That's because Solaris 10 'kadmin' uses RPCSEC_GSS and
> Wyllys> MIT uses a slightly different RPC protocol.
>
> [...]
>
> Wyllys> There have been patches submitted to the MIT codebase to make
> Wyllys> it able to support RPCSEC_GSS (and thus interop with
> Solaris kadmin),
> Wyllys> but Im not sure if those are in the latest release or not.
>
> RPCSEC_GSS support will be present in krb5-1.4 (currently in beta). I
> have done a brief successful interop test against SEAM's kadmin
> protocol. Independent confirmation would be useful.
>
> ---Tom
>
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
