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

Nico Williams <nico@cryptonector.com> Tue, 15 September 2015 15:35 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 0C54E1A03A6 for <kitten@ietfa.amsl.com>; Tue, 15 Sep 2015 08:35:26 -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 Gpcr2SJzihJE for <kitten@ietfa.amsl.com>; Tue, 15 Sep 2015 08:35:20 -0700 (PDT)
Received: from homiemail-a27.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 0E8AD1A0398 for <kitten@ietf.org>; Tue, 15 Sep 2015 08:35:20 -0700 (PDT)
Received: from homiemail-a27.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a27.g.dreamhost.com (Postfix) with ESMTP id 777AD598093; Tue, 15 Sep 2015 08:35:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:subject:message-id:references:mime-version:content-type :in-reply-to; s=cryptonector.com; bh=bjuSFwVAuAPReX8xDf5tFxooeNI =; b=F2RtdOo3Y09Mp29P3wC1jyIycwxBXFHXx2cda8Ja7r7tN53eHcT+nt6o449 ynvSVuPev3aGo8nDV9W0MB5QLcTJurdwyAmE45R1YLzFqdQnq1hTBDx0YjcIAe3E 7Jp/HHrpIwcyhjzEVvPxRMr1Bh8CKPvZOnlz57k1GytrMpXk=
Received: from localhost (108-207-244-100.lightspeed.austtx.sbcglobal.net [108.207.244.100]) (Authenticated sender: nico@cryptonector.com) by homiemail-a27.g.dreamhost.com (Postfix) with ESMTPA id 2329F598092; Tue, 15 Sep 2015 08:35:19 -0700 (PDT)
Date: Tue, 15 Sep 2015 10:35:17 -0500
From: Nico Williams <nico@cryptonector.com>
To: kitten@ietf.org
Message-ID: <20150915153516.GE13294@localhost>
References: <55F686EA.30206@openfortress.nl> <55F6EA7C.8070608@mit.edu> <20150914161100.GC13294@localhost> <55F6F843.2070609@openfortress.nl> <55F7C3FA.5090802@openfortress.nl> <20150915073030.GD21942@mournblade.imrryr.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20150915073030.GD21942@mournblade.imrryr.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/kitten/hyEPoBOQt1cYJtZWNJSHVE37TNM>
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 15:35:26 -0000

On Tue, Sep 15, 2015 at 07:30:30AM +0000, Viktor Dukhovni wrote:
> Text strings used to be handy for realm names in DNS when associated
> SRV records were plausibly optional.  These days, the REALM *should*
> be a DNS name.  Therefore, a simpler design would be:
> 
>     ; Realm mapping per-host reduces lookup latency
>     ;
>     _kerberos.host.name.example.com. IN PTR EXAMPLE.COM.

Clever.  I like this a lot.  For ASCII labels we even get the correct
case, whatever the server returns.  For IDNs, well, we haven't crossed
that river yet for Kerberos.

>     ; "Fallback" realm mapping at ancestor domain
>     ;
>     _kerberos.example.com. IN PTR EXAMPLE.COM.

The problem with the fallback thing is that we don't know how many
labels up to go, if any.  Should example.com. have an A RR but no
_kerberos.example.com., should we go ask com. what example.com.'s realm
should be?  Clearly not, but now try constructing a general rule...

>     ; Associated SRV records
>     ;
>     _kerberos._udp.example.com. IN SRV 0 100 88 kdc.example.com.
>     _kerberos._tcp.example.com. IN SRV 0 100 88 kdc.example.com.
> 
> This does not require a new RR type, PTR will do.

+1

Nico
--