Re: [openpgp] "OpenPGP Simple"

Phillip Hallam-Baker <phill@hallambaker.com> Sun, 22 March 2015 15:28 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A2D11A89E0 for <openpgp@ietfa.amsl.com>; Sun, 22 Mar 2015 08:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 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, 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 7bZ-IsKLQsOk for <openpgp@ietfa.amsl.com>; Sun, 22 Mar 2015 08:28:19 -0700 (PDT)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) (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 728171A8A07 for <openpgp@ietf.org>; Sun, 22 Mar 2015 08:28:14 -0700 (PDT)
Received: by lbbrr9 with SMTP id rr9so39114613lbb.0 for <openpgp@ietf.org>; Sun, 22 Mar 2015 08:28:13 -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=jhPWUU3xezQX5EsAnKMQPtAbDEoRYjUK8Htd/c9gBIs=; b=Gw9hHRVrWo2EwZ5tp/1EfWZFDFlnrNGBahLrb5aMr9xG92X87NzFarltf09qvpC69i BcGHgqZRh1209tTdlWAkN2QICLBOwnn04B0gOc1DUvRG2aH28lUO43SiOmPQe6QDqjEj UyvkdRteJ6hAV+BwkaFFFx6KBxoLIL3DVe1oOkoGlMSjvPq3qyAukPqCVFhzOmH4aWH0 PF7HiQZisOm7kvJFo8vrqglssPaElV49gRklPicAKGuyNucxc4eyE6mAovj54JGi7ksb GjXcUJn57aAaTaNmWGokx9lOwXmGS6NWcrvGeRhcTRlZ5NwWP9e4SXPBP4imeBMP21Vh 036g==
MIME-Version: 1.0
X-Received: by 10.112.151.226 with SMTP id ut2mr61995134lbb.55.1427038092982; Sun, 22 Mar 2015 08:28:12 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.45.203 with HTTP; Sun, 22 Mar 2015 08:28:12 -0700 (PDT)
In-Reply-To: <CAAS2fgQRM0-9U=NpyXnuugXiW+pxhP8x1J-hNsXpHB6H+M9dQQ@mail.gmail.com>
References: <9A043F3CF02CD34C8E74AC1594475C73AAFB984B@uxcn10-5.UoA.auckland.ac.nz> <CAMm+LwhA4OFqT1HTzzJNjC2fiSQ7++NNu9ZnLZyteAe87KcXug@mail.gmail.com> <CAAS2fgSUTB4dq+OdgrFm2xdgzvjiLQG+VAcq2emEFFJ9n9FfRg@mail.gmail.com> <CAMm+LwjhCYUv_WmU1N4zU7RJogK0Zo5C3DBieaKcDrG4rxU8Gg@mail.gmail.com> <CAAS2fgQRM0-9U=NpyXnuugXiW+pxhP8x1J-hNsXpHB6H+M9dQQ@mail.gmail.com>
Date: Sun, 22 Mar 2015 11:28:12 -0400
X-Google-Sender-Auth: ydzu5WyTGQAvgMnwf0DkUyEGeOc
Message-ID: <CAMm+LwjFVLuwKK9+2x4_7OEXvbcmpYR9YUW50TjAMTyAXM8C4w@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/PG9ZOgY4l_S7gJgpnL-531oXjV8>
Cc: "openpgp@ietf.org" <openpgp@ietf.org>, Peter Gutmann <pgut001@cs.auckland.ac.nz>
Subject: Re: [openpgp] "OpenPGP Simple"
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Mar 2015 15:28:20 -0000

On Sun, Mar 22, 2015 at 11:06 AM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
> On Sun, Mar 22, 2015 at 2:56 PM, Phillip Hallam-Baker
> <phill@hallambaker.com> wrote:
>> People keep telling me that canonicalization is necessary for
>> security. In 25 years I have never once heard someone give a use case
>> where it did.
>
> Okay, sure I can fix that problem for you, here is a recent example;
> look at OpenSSL CVE CVE-2014-8275
> (https://www.openssl.org/news/secadv_20150108.txt).
>
> A CA has signed an intermediate CA cert which is loaded in an
> interception appliance.  You blacklist this certificate by ID. Your
> blacklisting is bypassed by simply changing the encoding of the  when
> sending the cert chain and now your traffic can be intercepted again.
>
> (This isn't unique, but a recent example; if you're still thinking
> that you've still not had once usecase where it did I'd be glad to
> spend more time convincing you off-list)

Umm, I remain unconvinced. Basically this comes down to a defective
signature validation routine.

For revocation purposes the fingerprint should be taken over the
signedData blob or a subset thereof (e.g. keyinfo).

PKIX does not use the fingerprint for revocation, it uses the issuer
name and serial number.