[openpgp] ProtonMail moving to default X25519 keys

Sunny Rajan <sunny@protonmail.com> Tue, 15 January 2019 10:25 UTC

Return-Path: <sunny@protonmail.com>
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 E2CD9130DD3 for <openpgp@ietfa.amsl.com>; Tue, 15 Jan 2019 02:25:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=protonmail.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 6yQUPGtQWDxa for <openpgp@ietfa.amsl.com>; Tue, 15 Jan 2019 02:25:04 -0800 (PST)
Received: from mail4.protonmail.ch (mail4.protonmail.ch [185.70.40.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9714127133 for <openpgp@ietf.org>; Tue, 15 Jan 2019 02:25:03 -0800 (PST)
Date: Tue, 15 Jan 2019 10:24:54 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=default; t=1547547900; bh=CbfEbpJ5P0uRbpzDqJX4SX/PSj+00FQ8pWkGrMJB4Qc=; h=Date:To:From:Reply-To:Subject:Feedback-ID:From; b=EqWl2Sl1maSwsxu4FOinnYuZGWTq1G7lXqFyi5ZtoTXt0vYyU1BTFzxQl4USHTSdm 9DAvX4SFZ7XkYjyzQkgAqp8pVVo9dt/eOED3UXtGNlRv8xpgmYKv07qWlm8O0xquWW CCVtaY9a/ED862tAy0kh9DMK/kZYJXkLaazDYZhU=
To: "openpgp@ietf.org" <openpgp@ietf.org>
From: Sunny Rajan <sunny@protonmail.com>
Reply-To: Sunny Rajan <sunny@protonmail.com>
Message-ID: <94TsuhtP6GXVX2EUC8_FXEKKvVmGrIIeKcb286lH2gqkDZBBONDbyk8MyK_prHamSRKfb8lqMM6miq189Adpne3zt24wlfsRUR_36SZ5IS8=@protonmail.com>
Feedback-ID: Ly1pgPPPGPXYuEBAsukljrfFJyCohz3PKY6oGP6JwHpYl-g6c1wDhYpa5eH-NQSTtIXsia3nWE4gkKlLZA8gEg==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1_deaed8e8fdca2feb4bf30c653dbbd884"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/_GCmrofKP8kkBOQeUyKgCo5KPCA>
Subject: [openpgp] ProtonMail moving to default X25519 keys
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Jan 2019 10:25:07 -0000

Hello all,

At ProtonMail we are moving towards generating Ed25519/Curve25519 keys for our users by default on all clients. We realize this will cause interoperability issues with OpenPGP implementations that don't yet support X25519 encryption and signature verification, so we wanted to provide some advance notice in case you receive an increased number of reports from your users who are trying to communicate with ProtonMail users.
Please let us know if you have any concerns!

Best,
Sunny