[32084] in Kerberos

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

Re: another (different) KDC name resolution question

daemon@ATHENA.MIT.EDU (Tom Yu)
Mon Feb 22 19:21:01 2010

To: Russ Allbery <rra@stanford.edu>
From: Tom Yu <tlyu@mit.edu>
Date: Mon, 22 Feb 2010 19:20:40 -0500
In-Reply-To: <87mxz0zvqr.fsf@windlord.stanford.edu> (Russ Allbery's message of
	"Mon, 22 Feb 2010 15:38:52 -0800")
Message-ID: <ldvhbp8ol9j.fsf@cathode-dark-space.mit.edu>
MIME-Version: 1.0
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu

Russ Allbery <rra@stanford.edu> writes:

> Abe Singer <abe@ligo.caltech.edu> writes:
>
>> Well, that at least explains it.
>
>> You could call it a misfeature, or just an unanticipated consequence.
>> I suspect what we're doing here is a rare case.
>
> Actually, you are far from the only person to have had trouble with this.
> It's one of the more frequent complaints about the library behavior that
> I've seen, and it can cause some significant delays if one's DNS resolver
> is slow for some reason.

Thanks; this is useful input.  Working around the address resolution
latency issue probably requires redesign of some internal interfaces,
as Greg mentioned, so we will need to allocate resources accordingly.
I've added it to the roadmap.  If you and others could rank its
priority relative to the roadmap items that are already tentatively
slated for 1.9, that would also be helpful.

    http://k5wiki.kerberos.org/wiki/Roadmap
________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

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