Re: [kitten] Finding Kerberos Realm Descriptors in secure DNS

Nico Williams <nico@cryptonector.com> Tue, 15 September 2015 18:57 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF0591A92BD for <kitten@ietfa.amsl.com>; Tue, 15 Sep 2015 11:57:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.366
X-Spam-Level:
X-Spam-Status: No, score=-2.366 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jw_gLmyAaNU3 for <kitten@ietfa.amsl.com>; Tue, 15 Sep 2015 11:57:21 -0700 (PDT)
Received: from homiemail-a98.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1221AC3AB for <kitten@ietf.org>; Tue, 15 Sep 2015 11:57:18 -0700 (PDT)
Received: from homiemail-a98.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a98.g.dreamhost.com (Postfix) with ESMTP id A572955409A; Tue, 15 Sep 2015 11:57:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=KDJjcNz+4Qv3AM npxcfwJ1YEZYE=; b=Dt91PQ5f/6AlDhm+Xgu+5J31VPFASGU+TVfPDhWup1gwpX KrfHmalIdk5WeoEtLYqV9+Ods41rp+QeTx6SkG965A+Gji+pOxndMPxSAjqr32mu Sp37iD8mS9WBetMSYPWNHTBuV3Mk2p14IGBzSk+KjVIuGJhf0JNYLkSp7yaFA=
Received: from localhost (108-207-244-100.lightspeed.austtx.sbcglobal.net [108.207.244.100]) (Authenticated sender: nico@cryptonector.com) by homiemail-a98.g.dreamhost.com (Postfix) with ESMTPA id 0D77C55408E; Tue, 15 Sep 2015 11:57:07 -0700 (PDT)
Date: Tue, 15 Sep 2015 13:57:01 -0500
From: Nico Williams <nico@cryptonector.com>
To: Greg Hudson <ghudson@mit.edu>
Message-ID: <20150915185700.GI13294@localhost>
References: <55F686EA.30206@openfortress.nl> <55F6EA7C.8070608@mit.edu> <20150914161100.GC13294@localhost> <55F6F843.2070609@openfortress.nl> <20150914170757.GC13284@localhost> <55F72B14.8030409@openfortress.nl> <55F7C40F.9000509@openfortress.nl> <55F86534.50109@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <55F86534.50109@mit.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/kitten/feBFtiANzxpNYyDxu-ux_ljx_eU>
Cc: "kitten@ietf.org" <kitten@ietf.org>
Subject: Re: [kitten] Finding Kerberos Realm Descriptors in secure DNS
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2015 18:57:23 -0000

On Tue, Sep 15, 2015 at 02:36:36PM -0400, Greg Hudson wrote:
> On 09/15/2015 03:09 AM, Rick van Rein wrote:
> > See... we're requiring DNSSEC to validate the KREALM record, and it
> > is going to be difficult in general to rely on clients to accomadate
> > that; they may be subjected to crummy NAT routers that interfere
> > with, and break DNSSEC.  So, we will probably be dependent on KDCs
> > for practical deployment of KREALM, and a KDC could use KREALM
> > records to inspire a Server Referral in the style of RFC 6806.
> > 
> > So... it may be reasonable to assume that any KREALM client could
> > work with multiple realms, because they will normally be KDCs.  And
> > that'd mean we wouldn't need this priority or go-for-this-one flag.
> > Agreed?
> 
> A KDC can only return one referral, so I'm not sure what it would do
> with multiple realms, with or without priorities.  Perhaps I'm missing
> something.

Er, do we really want KDCs doing DNS queries for processing TGS-REQs?

I believe it could be done, and certainly LDAP and other things add
pressure to implement async evented KDCs, so that adding DNS queries
into the mix wouldn't be a big deal, but I suspect implementors are not
ready to bite that bullet.

Would this proposal (or variants discussed) really solve a _pressing_
problem?  Or a problem we believe will be pressing?

Nico
--