Re: [Trans] [trans] #79 (rfc6962-bis): Precertificate signature must be over something other than just the TBSCertificate

Erwann Abalea <eabalea@gmail.com> Mon, 30 March 2015 11:29 UTC

Return-Path: <eabalea@gmail.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18D6B1ACE19 for <trans@ietfa.amsl.com>; Mon, 30 Mar 2015 04:29:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 KKdE515MekOu for <trans@ietfa.amsl.com>; Mon, 30 Mar 2015 04:29:36 -0700 (PDT)
Received: from mail-yk0-x22d.google.com (mail-yk0-x22d.google.com [IPv6:2607:f8b0:4002:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E5B41ACE18 for <trans@ietf.org>; Mon, 30 Mar 2015 04:29:36 -0700 (PDT)
Received: by ykeg184 with SMTP id g184so7961646yke.2 for <trans@ietf.org>; Mon, 30 Mar 2015 04:29:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QLRfWDMeu6kv6gvnwDz25t6pYTDxLFyXap/3r9l8ITg=; b=EUpoesbnVkJyRq8twASMPz6ofPldrgKk4dos+410hbSO+SuJUMvVt8p2I2KFeBgKDY cr1lFA20I/qD1gQpUfUu/1Z0cQ2LgS0NC4aVYCHTZrTTJBGwyXMzOgBV91LI5aUOZJsE myeCzoWPqkAlaNreuyrWafy7hDybYqeCGKlNb9xtumKCL+6LRUNZ2R0jxf5eISsm162K QJikvJuRnif/mhQYWAq01szTwivfXZJgD67mX62n/aQ/51x9joEgg9kaky5+dBXYDzgP DA1d5vCQGznezy+AbYAu1we7JLJFA016eJxWNgoWRU8iyDdls/Tv77vjE3kNTf32YLNJ 7jdQ==
MIME-Version: 1.0
X-Received: by 10.52.155.3 with SMTP id vs3mr33954802vdb.63.1427714975414; Mon, 30 Mar 2015 04:29:35 -0700 (PDT)
Received: by 10.52.17.105 with HTTP; Mon, 30 Mar 2015 04:29:35 -0700 (PDT)
In-Reply-To: <064.abd6b6595a6018105f8527089cb573db@tools.ietf.org>
References: <064.abd6b6595a6018105f8527089cb573db@tools.ietf.org>
Date: Mon, 30 Mar 2015 13:29:35 +0200
Message-ID: <CA+i=0E7oqX5H7FUu-SXfH4Di2f0KoUAqnF0PyFPyvT22mSD+XQ@mail.gmail.com>
From: Erwann Abalea <eabalea@gmail.com>
To: trans issue tracker <trac+trans@tools.ietf.org>
Content-Type: multipart/alternative; boundary="089e01634a6ef33fd405127fcb1f"
Archived-At: <http://mailarchive.ietf.org/arch/msg/trans/fsZCnjY82jO-bUUtc1Dd_pfXScc>
Cc: Rob Stradling <rob.stradling@comodo.com>, "trans@ietf.org" <trans@ietf.org>, draft-ietf-trans-rfc6962-bis@tools.ietf.org
Subject: Re: [Trans] [trans] #79 (rfc6962-bis): Precertificate signature must be over something other than just the TBSCertificate
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Mar 2015 11:29:38 -0000

Specify that the EncapsulatedContentInfo MUST be some specific value
(allocate an OID from IETF/IANA/whatever).
RFC5652 states that if the EncapsulatedContentInfo is not id-data, then the
signedAttrs MUST be present (whence solution 2 will apply).

2015-03-27 17:08 GMT+01:00 trans issue tracker <trac+trans@tools.ietf.org>:

> #79: Precertificate signature must be over something other than just the
> TBSCertificate
>
>  If I understand the CMS spec correctly, then we're currently defining a
>  Precertificate to be a CMS structure that contains a TBSCertificate and a
>  signature over just that TBSCertificate.
>  That means that the components of a Precertificate can be trivially
>  rearranged into an X.509 certificate with a valid signature!
>
>  To fix this, we need to either...
>
>  1. Require the SignedData.encapContentInfo.eContent field to contain
>  "something || TBSCertificate" or "TBSCertificate || something".
>  or
>  2. Require a signed attribute to be present in
>  SignedData.signerInfos[0].signedAttrs.  This is essentially equivalent to
>  "TBSCertificate || something" in terms of what gets signed.
>
>  I think 2 is the cleaner solution, unless there's a cryptographic reason
>  to prefer "something || TBSCertificate" (e.g. to protect against chosen
>  prefix collisions?)
>
> --
> -------------------------------------+-------------------------------------
>  Reporter:                           |      Owner:  draft-ietf-trans-
>   rob.stradling@comodo.com           |  rfc6962-bis@tools.ietf.org
>      Type:  defect                   |     Status:  new
>  Priority:  blocker                  |  Milestone:
> Component:  rfc6962-bis              |    Version:
>  Severity:  -                        |   Keywords:
> -------------------------------------+-------------------------------------
>
> Ticket URL: <http://trac.tools.ietf.org/wg/trans/trac/ticket/79>
> trans <http://tools.ietf.org/trans/>
>
> _______________________________________________
> Trans mailing list
> Trans@ietf.org
> https://www.ietf.org/mailman/listinfo/trans
>



-- 
Erwann.