[38315] in Kerberos

home help back first fref pref prev next nref lref last post

Re: compile KDC with KKDCP support

daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Aug 28 02:08:46 2018

To: Jim Shi <hjshi@yahoo.com>, "kerberos@mit.edu" <kerberos@mit.edu>
From: Greg Hudson <ghudson@mit.edu>
Message-ID: <c7349ec5-142e-9b1b-edc0-a10bb3aac8df@mit.edu>
Date: Tue, 28 Aug 2018 02:08:25 -0400
MIME-Version: 1.0
In-Reply-To: <958677580.4688082.1535413648636@mail.yahoo.com>
Content-Language: en-US
Content-Type: text/plain; charset="utf-8"
Errors-To: kerberos-bounces@mit.edu
Content-Transfer-Encoding: 8bit

On 08/27/2018 07:47 PM, Jim Shi wrote:
> I have another questions.
> to compile KDC with kkdcp support, do I need pass in any special flag(s)?
> Or kkdcp is supported by default in recent code?

We have KKDCP support in the client library, but not natively in the 
KDC.  You can run a proxy KKDCP server using 
https://github.com/latchset/kdcproxy (available as kdcproxy in the 
Python package index).

> The reason I ask this question, is that when I run a test: (I do have kdc = https://.... configured for the realm). It does not seem to make https connection to the  server. Here is the trace log:
> host:~/test/bin] kdct$ env KRB5_TRACE=/dev/stdout ./kinit xxx@***
> init module "encrypted_timestamp", pa_type 2, flag 1

These messages look like output from compiling with -DDEBUG, not trace 
logs.  That syntax looks correct for setting KRB5_TRACE, so I'm not sure 
why you're not seeing trace logs.
Kerberos mailing list           Kerberos@mit.edu

home help back first fref pref prev next nref lref last post