IETF Logo Mail Archive

Re: [Acme] Signature misuse vulnerability in draft-barnes-acme-04

Phillip Hallam-Baker <phill@hallambaker.com> Thu, 13 August 2015 15:00 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F21F21A6F2E for <acme@ietfa.amsl.com>; Thu, 13 Aug 2015 08:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 aMLDfl-zObtD for <acme@ietfa.amsl.com>; Thu, 13 Aug 2015 08:00:33 -0700 (PDT)
Received: from mail-lb0-x241.google.com (mail-lb0-x241.google.com [IPv6:2a00:1450:4010:c04::241]) (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 57F7E1A21AC for <acme@ietf.org>; Thu, 13 Aug 2015 08:00:33 -0700 (PDT)
Received: by lbbtg9 with SMTP id tg9so2516486lbb.3 for <acme@ietf.org>; Thu, 13 Aug 2015 08:00:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ihB1MhryA5JSEoa5j/rAisVyFci5/R9S/LHXR2U+rTw=; b=qDUaF5JuvAfzVc8UPBR5DFlpQ/d18g5GhGqW+1RX2HsI6nL8+I9Ios/S6wAdTzt7ca kWvAylvzGriKos8StxKy/PhuLcHcxSgp+Y+x0Vzlns8IqHqGrtE31za8LwMT7WrLddlE ZTCbE96sUBwi29MEHSgIvyyZ09Y+rLiIlvI6btRZHVe+TJ+iOyD3yVlIW5ZP77DlRfpH a55Psl/5Oz6MD9c4qXBtwJZUMT9a7PBXQDoPoBATXKTfDLaCOnk981h53jOLF8Wn5UGI vKz9WHFwwO5Lpc9YLZvyCQnpXT2CnunXE6EM6R65+mXDmzRQ/BYK5alFikVlYcMxv2u1 VBnQ==
MIME-Version: 1.0
X-Received: by 10.152.87.169 with SMTP id az9mr36424026lab.46.1439478031817; Thu, 13 Aug 2015 08:00:31 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.10.20 with HTTP; Thu, 13 Aug 2015 08:00:31 -0700 (PDT)
In-Reply-To: <20150813145155.GA7501@LK-Perkele-VII>
References: <20150811085205.bbcd37b3b0bb0482f6522b1a@andrewayer.name> <CAL02cgRf2M0Gkqymif-=rmNG0v9hhaMC2SBiXf-n5aYiRKBnmQ@mail.gmail.com> <20150812160405.b824b673ad9b139a4fd9446f@andrewayer.name> <CAL02cgReCTMZ+ECiZVtv2=sNDng3mvEmGv4w6V_REbZ6xf75dw@mail.gmail.com> <55CC6BEC.6050706@cs.tcd.ie> <CAMm+Lwi4Y5J2w2TB=n78KQnRvS7f171k8rUjcD3RRu5PMNPPMQ@mail.gmail.com> <20150813145155.GA7501@LK-Perkele-VII>
Date: Thu, 13 Aug 2015 11:00:31 -0400
X-Google-Sender-Auth: ZhmuQ4fvNGjOtakPW77LrgVSqRk
Message-ID: <CAMm+LwgfD6bJYsNOKgwAG368zHU3b2_WLej0--5QCfCjW6NVAw@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Content-Type: multipart/alternative; boundary="001a11c240dcbfa17c051d3298ba"
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/XZEMEYzuZPogALWIaQ02glZbPuU>
Cc: Richard Barnes <rlb@ipv.sx>, "acme@ietf.org" <acme@ietf.org>, Andrew Ayer <agwa@andrewayer.name>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Acme] Signature misuse vulnerability in draft-barnes-acme-04
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Aug 2015 15:00:35 -0000

On Thu, Aug 13, 2015 at 10:51 AM, Ilari Liusvaara <
ilari.liusvaara@elisanet.fi> wrote:

> On Thu, Aug 13, 2015 at 10:27:09AM -0400, Phillip Hallam-Baker wrote:
> > +1
> >
> > I would much rather block the entire class of attacks rather than spend
> any
> > time working out if there is a way to do this with ECC based keys.
>
> FYI, one of the five proposals for CFRG signatures:
> - One is definitely vulernable (and key-checking won't help).
> - Two are definitely not vulernable.
> - Two I don't know.
>
> So good idea to just block the attack.
>

I hadn't actually thought of using this as a discrimination function on the
CFRG algorithms. It is as good as anything else.

v2.23.0 | Report a Bug | By Email