Re: [dane] Quick question regarding DANE and S/MIME

Viktor Dukhovni <ietf-dane@dukhovni.org> Sat, 15 April 2017 17:31 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: dane@ietfa.amsl.com
Delivered-To: dane@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15C9C12940B for <dane@ietfa.amsl.com>; Sat, 15 Apr 2017 10:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 14qT5TOYpQe3 for <dane@ietfa.amsl.com>; Sat, 15 Apr 2017 10:31:26 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9787A12422F for <dane@ietf.org>; Sat, 15 Apr 2017 10:31:26 -0700 (PDT)
Received: from dhcp-gs-2002.eduroam.cornell.edu (nat-128-84-124-0-978.cit.cornell.edu [128.84.127.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 9E5D17A32F1 for <dane@ietf.org>; Sat, 15 Apr 2017 17:31:25 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <9bb60f83-84cb-0e26-a6ac-3e65e57ef7bb@domblogger.net>
Date: Sat, 15 Apr 2017 13:31:25 -0400
Content-Transfer-Encoding: quoted-printable
Reply-To: IETF DANE Mailinglist <dane@ietf.org>
Message-Id: <F4200A77-78C1-44F4-8683-D296D4FA687F@dukhovni.org>
References: <9bb60f83-84cb-0e26-a6ac-3e65e57ef7bb@domblogger.net>
To: IETF DANE Mailinglist <dane@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dane/eBPX07XQiwQw4Y2HTFEPy4Hsdk8>
Subject: Re: [dane] Quick question regarding DANE and S/MIME
X-BeenThere: dane@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DNS-based Authentication of Named Entities <dane.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dane>, <mailto:dane-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dane/>
List-Post: <mailto:dane@ietf.org>
List-Help: <mailto:dane-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dane>, <mailto:dane-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Apr 2017 17:31:28 -0000

> On Apr 15, 2017, at 12:01 PM, Alice Wonder <alice@domblogger.net> wrote:
> 
> When using a 2 x x DANE record for S/MIME - Do I need to then include
> the intermediary (and root?) certificate with the actual user's certificate,
> or is it possible to use something like authorityInfoAccess when generating
> the cert to specify where the intermediary certificate that matches the DANE
> record resides?

The user's signature needs to (and generally will) include all the certificates
up to and including the "2 x x" trust-anchor.  To maximize the chance that this
will happen publish a "2 x x" for an intermediate, rather than a root (self-signed)
CA.

-- 
	Viktor.