[16332] in Kerberos_V5_Development
Re: Project Review: kinit -C
daemon@ATHENA.MIT.EDU (John Hascall)
Fri Sep 17 11:11:40 2010
To: Kerberos Devel list <krbdev@mit.edu>
In-reply-to: Your message of Fri, 17 Sep 2010 10:42:53 -0400.
<1284734573.5992.1773.camel@ray>
Date: Fri, 17 Sep 2010 10:11:31 CDT
Message-ID: <5522.1284736291@malison.ait.iastate.edu>
From: John Hascall <john@iastate.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
Greg Hudson <ghudson@mit.edu> answers:
> On Fri, 2010-09-17 at 07:58 -0400, John Hascall wrote:
> > I'm wondering why this would be. I'm thinking this isn't much more
> > than a config file and/or command line option a la '-i eth0' and
> > and an if-statement here or there. In fact, even in the absence of
> > multiple KDCs I would think restricting which interface you would
> > talk to might be a good thing.
> Feel free to take a look at kdc/main.c and lib/apputils/net-server.c and
> decide where you'd put the if statement here or there. :) I don't think
> it's impossible, but what we have right now is already kind of an
> octopus.
Sound like a re-factor might be in order :)
> > Also, perhaps I haven't been paying close enough attention, but what is
> > the use case for adding the complexity of automatically dealing with
> > network reconfiguration.
> The real-world use case is mini-KDCs running on laptops or other
> DHCP-configured computers. Obviously these are not traditional KDCs
> serving whole organizations, but see http://support.apple.com/kb/TS1452
> for instance.
Thanks. That makes a lot more sense now.
John
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
