Re: [openpgp] Fingerprint requirements for OpenPGP

Vincent Breitmoser <look@my.amazin.horse> Tue, 12 April 2016 13:15 UTC

Return-Path: <look@my.amazin.horse>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39BC912ED8A for <openpgp@ietfa.amsl.com>; Tue, 12 Apr 2016 06:15:51 -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 bGR0GzAZ64WL for <openpgp@ietfa.amsl.com>; Tue, 12 Apr 2016 06:15:49 -0700 (PDT)
Received: from mail.mugenguild.com (mugenguild.com [5.135.189.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9493012EDC3 for <openpgp@ietf.org>; Tue, 12 Apr 2016 06:15:49 -0700 (PDT)
Received: from localhost (dhcp176-217.wlan.rz.tu-bs.de [134.169.176.217]) by mail.mugenguild.com (Postfix) with ESMTPSA id B2D9C5FC83; Tue, 12 Apr 2016 15:15:47 +0200 (CEST)
Date: Tue, 12 Apr 2016 15:15:45 +0200
From: Vincent Breitmoser <look@my.amazin.horse>
To: Joseph Lorenzo Hall <joe@cdt.org>
Message-ID: <20160412131545.GA20078@littlepip.fritz.box>
References: <87vb3nslqh.fsf@alice.fifthhorseman.net> <20160412083409.GA16775@littlepip.fritz.box> <CABtrr-XdDjCXVCYSwUwL1cDGbv_ioNBg0Mpn3uf11oRm5TZ2ag@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl"
Content-Disposition: inline
In-Reply-To: <CABtrr-XdDjCXVCYSwUwL1cDGbv_ioNBg0Mpn3uf11oRm5TZ2ag@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/ngwj7Wyvib1uMmsM2ei7ylv18nA>
Cc: IETF OpenPGP <openpgp@ietf.org>
Subject: Re: [openpgp] Fingerprint requirements for OpenPGP
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 12 Apr 2016 13:15:51 -0000

Joseph Lorenzo Hall(joe@cdt.org)@Tue, Apr 12, 2016 at 09:06:11AM -0400:
> If you have two keys that map to the same fingerprint, then an
> attacker can decide to serve you whichever is in their best interest.

The premise of your scenario is that you are already using a key
generated by the attacker. What could an attacker possibly gain by
possessing a second key with the same fingerprint?

 - V