IETF Logo Mail Archive

Re: [smime] Message takeover attacks against S/MIME

Russ Housley <housley@vigilsec.com> Mon, 04 April 2016 15:07 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 63FD512D68E for <smime@ietfa.amsl.com>; Mon, 4 Apr 2016 08:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 4QtX8GKf_RgD for <smime@ietfa.amsl.com>; Mon, 4 Apr 2016 08:07:43 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 268B812D783 for <smime@ietf.org>; Mon, 4 Apr 2016 08:07:26 -0700 (PDT)
Received: from localhost (ronin.smetech.net [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 272D4F24087 for <smime@ietf.org>; Mon, 4 Apr 2016 11:07:26 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id SqsZBlecI6ND for <smime@ietf.org>; Mon, 4 Apr 2016 10:53:00 -0400 (EDT)
Received: from dhcp-b4d9.meeting.ietf.org (dhcp-b4d9.meeting.ietf.org [31.133.180.217]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 629B3F2403D for <smime@ietf.org>; Mon, 4 Apr 2016 11:07:25 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <FB7111D8-F91C-41FD-AE0D-E4C938195B14@vigilsec.com>
Date: Mon, 04 Apr 2016 11:07:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C576E39F-BD13-4C39-984E-8AAC423DB159@vigilsec.com>
References: <B3640A5E-C644-4E53-8FDD-D7FBE87F300D@vigilsec.com> <9A043F3CF02CD34C8E74AC1594475C73F4BDB8A8@uxcn10-5.UoA.auckland.ac.nz> <56d70399.8d41620a.19ae8.ffffeb3bSMTPIN_ADDED_MISSING@mx.google.com> <FB7111D8-F91C-41FD-AE0D-E4C938195B14@vigilsec.com>
To: IETF SMIME <smime@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/smime/TGT7XPBDb-gHAiS-eocgzoy33hc>
Subject: Re: [smime] Message takeover attacks against S/MIME
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 04 Apr 2016 15:07:47 -0000

Regarding item 2, we already have RFC 5084 that specifies the use of AES-CCM and AES-GCM with CMS.  I have just posted an I-D that specifies the use of ChaCha20 with Poly1305 with CMS:

	https://www.ietf.org/id/draft-housley-cms-chacha20-poly1305-00.txt

Please read and review.

Russ


On Mar 8, 2016, at 1:58 AM, Russ Housley <housley@vigilsec.com> wrote:

> I am hearing interest in these topics (a combination of things on this list and side conversations).
> 
> (1) Specify the way to use authenticated encryption in S/MIME.  Note that it is already done for CMS.
> 
> (2) Specify conventions for AES-CCM, AES-GCM, and ChaCha20 with Poly1305 authenticated encryption algorithms.
> 
> (3) Specify conventions for using Curve25519 and Curve448 for key agreement.
> 
> (4) Specify conventions for using the CFRG chosen curves for elliptic curve digital signature.
> 
> (5) Specify a way to use PGP public keys in addition to PKIX certificates.
> 
> Anything else?
> 
> Is this enough to re-charter the S/MIME WG?
> 
> Russ

v2.23.0 | Report a Bug | By Email