IETF Logo Mail Archive

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

Jacob Hoffman-Andrews <jsha@eff.org> Thu, 13 August 2015 17:25 UTC

Return-Path: <jsha@eff.org>
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 791991A8954 for <acme@ietfa.amsl.com>; Thu, 13 Aug 2015 10:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.012
X-Spam-Level:
X-Spam-Status: No, score=-7.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 9UfSQ8SZ5T0e for <acme@ietfa.amsl.com>; Thu, 13 Aug 2015 10:25:14 -0700 (PDT)
Received: from mail2.eff.org (mail2.eff.org [173.239.79.204]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F3DF1A8A4D for <acme@ietf.org>; Thu, 13 Aug 2015 10:25:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=eff.org; s=mail2; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=6kFC/GUwnLiyeDUE9BZ2v7uH+FuWwYzFkyBu2aAB2Ds=; b=5FjQkyC60o9Z9kvSl2Mk2edHwyPrgUfZ9h+Pv8yphYX8UeOvtGG7AEtEYi8g9lZKg/CvkWggmZfwyIlzQ34+EbIA9EkT8U22v/RcTG4UIXdNrtB/Mph1YkTjTxLtjN51kR0oyv9fx6WTg37J3G3ONYGFGhg0mlgcgQx2IXA6JjQ=;
Received: ; Thu, 13 Aug 2015 10:25:00 -0700
Message-ID: <55CCD2EA.5080006@eff.org>
Date: Thu, 13 Aug 2015 10:24:58 -0700
From: Jacob Hoffman-Andrews <jsha@eff.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: Eric Mill <eric@konklone.com>, Richard Barnes <rlb@ipv.sx>
References: <20150811085205.bbcd37b3b0bb0482f6522b1a@andrewayer.name> <CAL02cgRf2M0Gkqymif-=rmNG0v9hhaMC2SBiXf-n5aYiRKBnmQ@mail.gmail.com> <20150812160405.b824b673ad9b139a4fd9446f@andrewayer.name> <CAL02cgReCTMZ+ECiZVtv2=sNDng3mvEmGv4w6V_REbZ6xf75dw@mail.gmail.com> <CANBOYLX8wGaYi_6_cV9Jp-aBRW9SqtOQZBBCih0dz9Za2-iVbA@mail.gmail.com> <CAL02cgSM3BAnxattcgm=J2pvi2LPeTYm+rD2JVu+uNvvgmZsCA@mail.gmail.com> <CANBOYLXJrPHB=0vE9ewOg5O6AR56L2jpt7aSj0_9cb19YahTUg@mail.gmail.com>
In-Reply-To: <CANBOYLXJrPHB=0vE9ewOg5O6AR56L2jpt7aSj0_9cb19YahTUg@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Received-SPF: skipped for local relay
Received-SPF: skipped for local relay
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/HCsWkSIJd3m3ZcB5yKXeFskaBtY>
Cc: "acme@ietf.org" <acme@ietf.org>, Andrew Ayer <agwa@andrewayer.name>
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 17:25:16 -0000

> Yep, I get that. I might be misreading it, but it looked like the
> suggestion of a /.well-known URI for account keys would impact all
> ACME users, not just those using Simple HTTP validation.
I didn't fully expand the idea, but my assumption was that similar
continuous publication techniques could apply to other challenge types.
For instance, DVSNI could involve answering for a
<identifier>.acme.invalid at any time with a test certificate embedding
a list of account keys or account key hashes in some format. Similarly,
one could publish a list of account key hashes in DNS.

v2.23.0 | Report a Bug | By Email