Re: [smime] [Technical Errata Reported] RFC2631 (5954)

Russ Housley <housley@vigilsec.com> Wed, 08 January 2020 15:17 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: smime@ietfa.amsl.com
Delivered-To: smime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA4EE120180 for <smime@ietfa.amsl.com>; Wed, 8 Jan 2020 07:17:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 Tar5T4162Jbo for <smime@ietfa.amsl.com>; Wed, 8 Jan 2020 07:17:33 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 038D8120127 for <smime@ietf.org>; Wed, 8 Jan 2020 07:17:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 66348300AE1 for <smime@ietf.org>; Wed, 8 Jan 2020 10:17:31 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 0cCFkuXVr4E6 for <smime@ietf.org>; Wed, 8 Jan 2020 10:17:28 -0500 (EST)
Received: from [5.5.33.19] (unknown [204.194.23.17]) by mail.smeinc.net (Postfix) with ESMTPSA id 2F2AE30078C; Wed, 8 Jan 2020 10:17:28 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20200108033645.GA57294@kduck.mit.edu>
Date: Wed, 8 Jan 2020 10:17:28 -0500
Cc: IETF SMIME <smime@ietf.org>, "Roman D. Danyliw" <rdd@cert.org>, Eric Rescorla <ekr@rtfm.com>, silversplash@gmx.com, paul.hoffman@vpnc.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <875F9475-2444-472E-9B1B-AF8C8691163B@vigilsec.com>
References: <20200102204220.C652DF40707@rfc-editor.org> <20200108033645.GA57294@kduck.mit.edu>
To: Ben Kaduk <kaduk@mit.edu>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/Z5zjmwmbT6KVbAd9LAvw5BnJhxg>
Subject: Re: [smime] [Technical Errata Reported] RFC2631 (5954)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/smime/>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2020 15:17:35 -0000

Ben:

It sounds like Hold for Document Update is the best way to handle this one.

Russ

> On Jan 7, 2020, at 10:36 PM, Benjamin Kaduk <kaduk@mit.edu> wrote:
> 
> I could maybe see making this Hold For Document Update, as it would
> probably require some discussion, and it's hard to say that this was an
> omission at the time of original publication.
> 
> -Ben
> 
> On Thu, Jan 02, 2020 at 12:42:20PM -0800, RFC Errata System wrote:
>> The following errata report has been submitted for RFC2631,
>> "Diffie-Hellman Key Agreement Method".
>> 
>> --------------------------------------
>> You may review the report below and at:
>> https://www.rfc-editor.org/errata/eid5954
>> 
>> --------------------------------------
>> Type: Technical
>> Reported by: Paul Janson <silversplash@gmx.com>
>> 
>> Section: 2.1.5.
>> 
>> Original Text
>> -------------
>>     1. Verify that y lies within the interval [2,p-1]. If it does not,
>>        the key is invalid.
>>     2. Compute y^q mod p. If the result == 1, the key is valid.
>>        Otherwise the key is invalid.
>> 
>> 
>> Corrected Text
>> --------------
>>     1. Verify that y lies within the interval [2,p-1]. If it does not,
>>        the key is invalid.
>>     2. Compute y^q mod p. If the result == 1, the key is valid.
>>        Otherwise the key is invalid.
>> |    3. Verify that y does not match g.
>> 
>> 
>> Notes
>> -----
>> Validating that (g == received y) needs to be an additional exclusion to the valid range [2,p-1]. If party 'a' accepts received public key 'yb' matching 'g', then ZZ matches  public key 'ya'. i.e. if yb = 2, then xb = 1, therefore ZZ = ya^1 = ya
>> 
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party  
>> can log in to change the status and edit the report, if necessary. 
>> 
>> --------------------------------------
>> RFC2631 (draft-ietf-smime-x942-07)
>> --------------------------------------
>> Title               : Diffie-Hellman Key Agreement Method
>> Publication Date    : June 1999
>> Author(s)           : E. Rescorla
>> Category            : PROPOSED STANDARD
>> Source              : S/MIME Mail Security
>> Area                : Security
>> Stream              : IETF
>> Verifying Party     : IESG
> 
> _______________________________________________
> smime mailing list
> smime@ietf.org
> https://www.ietf.org/mailman/listinfo/smime