[saag] Best practices for verifying authenticity of OpenPGP keys?
Yakov Shafranovich <yakov@nightwatchcybersecurity.com> Thu, 15 April 2021 02:33 UTC
Return-Path: <yakov@nightwatchcybersecurity.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D2353A2A3D for <saag@ietfa.amsl.com>; Wed, 14 Apr 2021 19:33:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nightwatchcybersecurity-com.20150623.gappssmtp.com
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 15laNBsvjjV3 for <saag@ietfa.amsl.com>; Wed, 14 Apr 2021 19:33:25 -0700 (PDT)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (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 7C5C93A2A3F for <saag@ietf.org>; Wed, 14 Apr 2021 19:33:25 -0700 (PDT)
Received: by mail-wm1-x32b.google.com with SMTP id b136-20020a1c1b8e0000b029012c69da2040so4122096wmb.1 for <saag@ietf.org>; Wed, 14 Apr 2021 19:33:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nightwatchcybersecurity-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=1pIirE+Jo0UbrZ8VnGdAKmJoCjaKGkK9OPSb4G791+Y=; b=ggYEdk+3GWXyxJ09hB02Dby7SI271yoxV7w0kjmKYSGGKpVcvWj8pBzBdv+yuDTf/k n7HN+kM4YlWezQ5JvDj4yEHhFu551G6m0qVq8E9UfOTto0bcZEIBHE4ElLuIxzwaH8W0 P5URFHYEp/16gIIolHqXlV04iHfUcBUuzDmFJ5pKwggFvxQWIo6tYRaMyj203Nn6T9ZM BN/Ebp0SY9aykmcrwpNDsClK7yw9FuywSO4KJUse6N1I5oYDnxH+Ox8tR3qhwodF6RGm 5NApmun3mHNGxx9lyAGYaCwsSYtXvQnKxOVUXErDbcNgoWKEI8ufWtPkNr4DObgg41su u0Vw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=1pIirE+Jo0UbrZ8VnGdAKmJoCjaKGkK9OPSb4G791+Y=; b=kWpV3Or7OT68cx8R3crYDGzKkrV0LhXLGH/2hoS+VeC9rG+poitRauGoDU8dagcvd4 0hURAso2yTZUM3iQNhmCgudfwxH0Pd6R3qZPU9SkQzkujULpmc+vGvpNk/j9UZisII4K GsWo9s8G/K8Trn2o0p4jgnacEWL5GJ3Jfk90S9cgTWn3L1encK99+v72czvpFrVFxZsm p+R4n6Y8kSREl6TOn2ONABtF6E2mPLShmB2wEL4YNpArsj3E5k+lR02UrkhTTPaJTw+E K62ioIeaCyazxiEs7wLoOS/qDntF1W1hqKzvLZSVV5oHgTwEUgnBTZ/0+pKq1ODDmsgC Sj7A==
X-Gm-Message-State: AOAM533SRtAZpLQFZie+A4X191Si68YFVnAGZlzCcLVysV0FIK23KX8A nmqcWvj84uJ0ap0zthe/QrPGDIZU71QgrGNXJ+RyDKsBMKEddQ==
X-Google-Smtp-Source: ABdhPJw5CDZKXa7k/fDaEjpmojTZYfG54aH+4V/DBthXcaKYCriLeXtt36q8mdnFsezrBkQ1W+k2HfA7/rcEjoL8P7M=
X-Received: by 2002:a05:600c:20c:: with SMTP id 12mr726465wmi.138.1618454002049; Wed, 14 Apr 2021 19:33:22 -0700 (PDT)
MIME-Version: 1.0
From: Yakov Shafranovich <yakov@nightwatchcybersecurity.com>
Date: Wed, 14 Apr 2021 22:32:47 -0400
Message-ID: <CAAyEnSNCTWL-qiKW=4bm6ySv1Suv7Vwwe3tnXDKSBBZFPAotZg@mail.gmail.com>
To: saag@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/y41n0mOhSaDRJGp-55Zln4ok-tM>
Subject: [saag] Best practices for verifying authenticity of OpenPGP keys?
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Apr 2021 02:33:31 -0000
(this is another issue that was recently raised by an implementer of "security.txt") What is the current best practice for verifying whether a given OpenPGP key is real and valid? Not clear if Web of Trust is widely used anymore, PKI isn't applicable and public keyservers have been targeted in the past by poisoning attacks. To me, the most common approach seems to be publishing the keys or their fingerprints on the web where they can be retrieved with TLS, essentially relying on public PKI. This appears to be the approach used by OpenSSL, Tails, Tor, etc. See: https://www.openssl.org/community/omc.html https://tails.boum.org/install/mac/usb-download/index.en.html https://support.torproject.org/tbb/how-to-verify-signature/ Thanks
- [saag] Best practices for verifying authenticity … Yakov Shafranovich
- Re: [saag] Best practices for verifying authentic… Simon Josefsson
- Re: [saag] Best practices for verifying authentic… Randy Bush