Received: from pch.mit.edu (PCH.MIT.EDU [18.7.21.90]) by krbdev.mit.edu (8.9.3p2) with ESMTP id PAA17641; Wed, 18 Aug 2004 15:38:37 -0400 (EDT)
Received: from pch.mit.edu (localhost [127.0.0.1]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i7IJcal1008473 for <krb5-send-pr@krbdev.mit.edu>; Wed, 18 Aug 2004 15:38:36 -0400 (EDT)
Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i7GHjgl1015706 for <krb5-bugs-incoming@PCH.mit.edu>; Mon, 16 Aug 2004 13:45:42 -0400 (EDT)
Received: from exch-one.centrify.com (adsl-64-166-65-50.dsl.sntc01.pacbell.net [64.166.65.50])i7GHjfOe011787 for <krb5-bugs@mit.edu>; Mon, 16 Aug 2004 13:45:41 -0400 (EDT)
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Date: Mon, 16 Aug 2004 10:45:40 -0700
Message-Id: <D6DE73398967E54096684518594D99310465D8@exch-one.centrify.com>
X-Mimeole: Produced By Microsoft Exchange V6.5.7226.0
X-MS-Has-Attach: 
X-MS-Tnef-Correlator: 
Thread-Topic: Custom kdc lookup
Thread-Index: AcSDtcnAuBh85H0sRpijCAzzbBmI/gAAvb/Q
From: "Paul Moore" <paul.moore@centrify.com>
To: <krb5-bugs@mit.edu>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by pch.mit.edu id i7GHjgl1015706
X-Mailman-Approved-At: Wed, 18 Aug 2004 15:38:35 -0400
Subject: FW: Custom kdc lookup
X-Beenthere: krb5-bugs-incoming@mit.edu
X-Mailman-Version: 2.1
Precedence: list
Sender: krb5-bugs-incoming-bounces@mit.edu
Errors-To: krb5-bugs-incoming-bounces@mit.edu
X-RT-Original-Encoding: us-ascii
Content-Length: 679

 
I dont know if this is an old topic or not.
I would like to replace the mechanism that kerberos uses for locating 
KDCs.
My proposal would be to allow the calling application to do something 
along these lines
 
krb5_set_locator(<context, <my locator function>);
 
This function sets a callback pointer in the context block And then 
have krb5_locate_kdc look to see of this function pointer is non null 
and if so call <my function> instead of the standard sequence.
Of course I could simply hack this into the code base but would much 
prefer to have it in the main code line. It seems that this could be 
useful for many people with non standard kdc discovery processes.