Date: Thu, 24 May 2012 13:17:21 -0400
From: Nalin Dahyabhai <nalin@redhat.com>
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #6742] would like to be able to specify listening address for krb5kdc and kadmind
Message-ID: <20120524171721.GA2268@redhat.com>
References: <rt-6742@krbdev.mit.edu> <rt-6742-35536.12.30240095365@krbdev.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <rt-6742-35536.12.30240095365@krbdev.mit.edu>
Organization: Red Hat, Inc.
User-Agent: Mutt/1.5.21 (2010-09-15)
RT-Send-Cc: 
Content-Length: 851

On Thu, May 24, 2012 at 12:04:30PM -0400, Greg Hudson via RT wrote:
> We have someone interested in solving this issue.  Do you think it would 
> be sufficient to add an inetd option to krb5kdc?
> 
> Because we serve over UDP and TCP, and because correctly implementing a 
> UDP server in the Unix socket interface is more difficult than it should 
> be, our server network loop is very complicated.  Deferring this issue to 
> inetd would have a small UI footprint and would add a small amount of 
> additional complexity.  Adding specific address configuration would have a 
> larger UI footprint and a larger increase in complexity, I expect.  But 
> it's something we could still consider.

It sounds like it could.  Would such a setup end up firing up a
different KDC (or kadmind) process for each listening address that
received traffic?

Nalin