Re: What ASN.1 got right

Nico Williams <nico@cryptonector.com> Wed, 03 March 2021 02:17 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06A933A16A0 for <ietf@ietfa.amsl.com>; Tue, 2 Mar 2021 18:17:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level:
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
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 33q3EwHqcMeQ for <ietf@ietfa.amsl.com>; Tue, 2 Mar 2021 18:17:39 -0800 (PST)
Received: from cockroach.elm.relay.mailchannels.net (cockroach.elm.relay.mailchannels.net [23.83.212.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 915FF3A169E for <ietf@ietf.org>; Tue, 2 Mar 2021 18:17:39 -0800 (PST)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 6AB733624D7; Wed, 3 Mar 2021 02:17:38 +0000 (UTC)
Received: from pdx1-sub0-mail-a14.g.dreamhost.com (100-96-10-164.trex.outbound.svc.cluster.local [100.96.10.164]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id EC54C36231A; Wed, 3 Mar 2021 02:17:37 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a14.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.96.10.164 (trex/6.0.2); Wed, 03 Mar 2021 02:17:38 +0000
X-MC-Relay: Good
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Shoe-Towering: 6dfda4623822d4f4_1614737858210_3844375071
X-MC-Loop-Signature: 1614737858210:747356566
X-MC-Ingress-Time: 1614737858210
Received: from pdx1-sub0-mail-a14.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a14.g.dreamhost.com (Postfix) with ESMTP id AF5A57E3D7; Tue, 2 Mar 2021 18:17:37 -0800 (PST)
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=OBn/mWeDQ74KEE ExkIpDqwm/gr4=; b=qhVnoIq40C1iMo0/I24CCLGwQJu+pCU9RFO+I0g4sGeezB nVgHHo/ICbVwV+XhCtq8PE+7iCMTPaf3K26PEACCjq3eb/V8HTYpNKewpvpiSUuG 30lwxD2oP4vuFBxjBhHByMWHyG1CHGFcazJAwY3NdCOCdLA9pxsKz6+/W7xlc=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a14.g.dreamhost.com (Postfix) with ESMTPSA id E98447E3D2; Tue, 2 Mar 2021 18:17:35 -0800 (PST)
Date: Tue, 2 Mar 2021 20:17:33 -0600
X-DH-BACKEND: pdx1-sub0-mail-a14
From: Nico Williams <nico@cryptonector.com>
To: Michael Thomas <mike@mtcc.com>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: What ASN.1 got right
Message-ID: <20210303021731.GD30153@localhost>
References: <CAMm+LwiEqL3bMg09e5NBNZwkPJ90DmQgLTy=SQNEN0q=vp=wrQ@mail.gmail.com> <ed6830b3-e650-d3fa-b253-9f53e01f9615@mtcc.com> <CAMm+LwifpPg-Sg9cXLpWvjmExt8KfuYq6oRZd4D1L0ZBR3nRFg@mail.gmail.com> <1631e20d-9d8a-b8c2-9d5e-6c7f4defa72d@mtcc.com> <20210302234928.GX30153@localhost> <cb4960e2-05a1-9d28-f17b-9f610ac378c9@mtcc.com> <20210303002330.GZ30153@localhost> <7d70044c-88e8-0165-5ce3-4c8612965f16@mtcc.com> <20210303005747.GC30153@localhost> <13c4899d-9893-4a9e-3deb-904367ad2e35@mtcc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <13c4899d-9893-4a9e-3deb-904367ad2e35@mtcc.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MYhvuL2n5eNF_frJPpbvdk5AChc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2021 02:17:41 -0000

On Tue, Mar 02, 2021 at 05:09:06PM -0800, Michael Thomas wrote:
> > > > > Is anybody using PKINIT?
> > > > Yes.
> > > Where? In any volume?
> > Corporate networks.  The only place where Kerberos is used.
> 
> Really? What is the use case? I'm under the impression that Kerberos has
> mostly been relegated to Active Directory and that's about it. I like
> Kerberos, fwiw.

Use cases:

 - smartcards

 - anonymous Kerberos (requires PKINIT)

 - batch jobs

   You can have a trust anchor where a CA issues certificates with a
   Kerberos SAN and the PKINIT EKU and then that can be used to get
   tickets on behalf of that user for their batch jobs.

I don't like Kerberos, not Kerberos V, but I do like Needham-Schroeder,
and I suspect we may want to sprinkle a bit of Needham-Schroeder onto
a post-quantum future as an optimization for PQ crypto.

Nico
--