Re: [Spasm] Document Updates

Russ Housley <housley@vigilsec.com> Mon, 13 March 2017 20:01 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28EE9129A92 for <spasm@ietfa.amsl.com>; Mon, 13 Mar 2017 13:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 PoPYGlh5xzbX for <spasm@ietfa.amsl.com>; Mon, 13 Mar 2017 13:01:11 -0700 (PDT)
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 06D0612949D for <spasm@ietf.org>; Mon, 13 Mar 2017 13:01:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 6014930041B for <spasm@ietf.org>; Mon, 13 Mar 2017 16:01:10 -0400 (EDT)
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 gQS_q0jjyutg for <spasm@ietf.org>; Mon, 13 Mar 2017 16:01:09 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 51FA130048E for <spasm@ietf.org>; Mon, 13 Mar 2017 16:01:09 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Mon, 13 Mar 2017 16:01:08 -0400
References: <0bea01d29c31$b4930430$1db90c90$@augustcellars.com>
To: SPASM <spasm@ietf.org>
In-Reply-To: <0bea01d29c31$b4930430$1db90c90$@augustcellars.com>
Message-Id: <5701426C-F82E-4E2E-9205-50F11FEC0F88@vigilsec.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/nCb89i5Yzb1HkJ6ik3SB_Ccm5I4>
Subject: Re: [Spasm] Document Updates
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Mar 2017 20:01:12 -0000

> I have released new versions of the two S/MIME documents to address all last
> call comments received.
> 
> I have not dealt with one comment which has to do with the first default
> algorithm to be used for encryption when there is no knowledge of what the
> recipient of the message is capable of.  This has traditionally always been
> the "best possible recommendation" that we can provide.  For this reason, I
> have set it to AES-128 GCM.  
> 
> Russ has requested that this be changed to AES-256 CBC because we are
> introducing not only a new algorithm but a new CMS structure at the same
> time.  This means that not only would a down client be unable to decrypt the
> message but would not recognize it as being an encrypted message. 
> 
> I do not really think that I care about this possible problem as it should
> be dealt with cleanly, an ASN.1 decode error needs to be coped with.  For
> this reason I do not think there is going to be a significant behavior
> difference between an ASN.1 decode/message type recognition problem and a
> cannot decrypt because the algorithm is unknown.

Implementer’s please state you preference.