[6831] in Kerberos
Re: Using DCE secd as a Kerberos 5 KDC (fwd)
daemon@ATHENA.MIT.EDU (Mark Champine)
Wed Mar 6 14:20:44 1996
To: kerberos@MIT.EDU
In-Reply-To: Your message of "Tue, 05 Mar 1996 23:56:52 -0400."
<v02120d06ad62bc2fb92a@[199.33.247.8]>
Date: Wed, 06 Mar 1996 13:58:12 -0500
From: Mark Champine <champine@apollo.hp.com>
>>Subject: Using DCE secd as a Kerberos 5 KDC
>>
>>Hello,
>>
>>Short question. Has anyone actually done this? I am aware of the OSF RFC 92.0
>>January 1996 that describes the intent to provide interoperability in DCE 1.2.2
>>(and support berkeley r commands - yeah!). But has anyone done it with
>>existing DCE products.
While there are many issues (as you've seen in RFC 92.0) the combination
is generally workable. If you use Beta5, make sure you get Doug
Engert's patch at ftp://achilles.ctd.anl.gov/pub/kerberos.v5
I believe the file you want is k55.cdiff.951031
> As I indicated in a seperate note, the Betas that I believe are currently
> workable in this scenario are Beta 3, 5 & 6.
V5 B4 Patch 1 & 3 libraries, also work for building client apps that
can use either the DCE secd or Kerberos KDC. Beta4 has the
advantage of using the same /krb5/krb.conf file format as DCE.
secd can also be configured to work with V5 B2 & 3, at the expense of
sacrificing DCE 1.0 compatibility.
M.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Mark Champine, Hewlett-Packard CHR-03-CE, 300 Apollo Drive
Chelmsford MA 01824 (508)436-4292 champine@apollo.hp.com DCE Security
