IETF Logo Mail Archive

Re: [kitten] Is id-pkinit-san misnamed? Can it be reused by kca?

Nico Williams <nico@cryptonector.com> Thu, 05 December 2013 07:28 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 B7EFA1A8034 for <kitten@ietfa.amsl.com>; Wed, 4 Dec 2013 23:28:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] 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 Z_13NZ2NP3lL for <kitten@ietfa.amsl.com>; Wed, 4 Dec 2013 23:28:06 -0800 (PST)
Received: from homiemail-a104.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by ietfa.amsl.com (Postfix) with ESMTP id 7B9901A1F78 for <kitten@ietf.org>; Wed, 4 Dec 2013 23:28:06 -0800 (PST)
Received: from homiemail-a104.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a104.g.dreamhost.com (Postfix) with ESMTP id 617532005D105 for <kitten@ietf.org>; Wed, 4 Dec 2013 23:28:03 -0800 (PST)
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=bbOejoH1TsaOJSTqIYic0gfHnJ0 =; b=kqn96Em5PIjI71riard5AHssAbDTgPek2aOncc2Lcm6k1/5EHaj+EWAOrB1 6NtbdmSbo4RQGU0XBMKR/1F5hqD9oIBbnBnW/43sI72ATcyBp9JJbYPSixHRPO2E 6yIptbT5n1A1he7c3S1cZBzmO9TkDAnd013aBur4aaILd4fE=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a104.g.dreamhost.com (Postfix) with ESMTPA id 1570D2005D102 for <kitten@ietf.org>; Wed, 4 Dec 2013 23:28:03 -0800 (PST)
Date: Thu, 05 Dec 2013 01:28:02 -0600
From: Nico Williams <nico@cryptonector.com>
To: kitten@ietf.org
Message-ID: <20131205072759.GR21240@localhost>
References: <20131205071852.GO21240@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20131205071852.GO21240@localhost>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [kitten] Is id-pkinit-san misnamed? Can it be reused by kca?
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: <http://www.ietf.org/mail-archive/web/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: Thu, 05 Dec 2013 07:28:07 -0000

On Thu, Dec 05, 2013 at 01:18:55AM -0600, Nico Williams wrote:
> ...unless one *really* wants to use Kerberos->kx509->PKINIT as a form of
> PKCROSS... :)
> 
> ...which conveniently just happens to be my proposal for PKCROSS!

Sidebar:

PKINIT ASes would need to encode the certification trust path of their
clients as Kerberos transited paths.

And we'd have more pressure to support X.500-style names in transit
paths (and transit path validation policies), though at least PKINIT
ASes could insist that foreign-realm client cert issuers have
id-pkinit-sans in their issuer certs so as to avoid having to have
X.500-style names in transit paths.

v2.30.2 | Report a Bug | By Email | System Status