Re: [openpgp] ProtonMail moving to default X25519 keys
Bart Butler <bartbutler@protonmail.com> Tue, 15 January 2019 19:05 UTC
Return-Path: <bartbutler@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 492A9130F06 for <openpgp@ietfa.amsl.com>; Tue, 15 Jan 2019 11:05:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, 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 rMvdIZbCTFKI for <openpgp@ietfa.amsl.com>; Tue, 15 Jan 2019 11:05:02 -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 5F197130F0F for <openpgp@ietf.org>; Tue, 15 Jan 2019 11:05:02 -0800 (PST)
Date: Tue, 15 Jan 2019 19:04:54 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=default; t=1547579100; bh=Ndp1yiB8INDKlTQuhhOWFHCLvQx6BcKl0QqeM4eJRpM=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References: Feedback-ID:From; b=JIDsQ6HXu/77aeZs90tb4kbWdWmPEIGbwS9j8yGELe/nCXq7qeDBvk3/tcUSm1aMz XrPH/4HMAWhp1s6dVTx3kvnzccZHyQ/e/mw7qKPRhSb1qYf3wreG19U3ADruWK1jIv Me7bHa9tsl/Nq2s3YYqo4kLgK4vvDwKkVEvCD2do=
To: Vincent Breitmoser <look@my.amazin.horse>
From: Bart Butler <bartbutler@protonmail.com>
Cc: "openpgp@ietf.org" <openpgp@ietf.org>, Sunny Rajan <sunny@protonmail.com>
Reply-To: Bart Butler <bartbutler@protonmail.com>
Message-ID: <RoWJFgoTpYuS36aJQ2_tD7fI1liv-ke-pTzk5PG1c4E2ZKmAvnZ-Nsm5_By7BhxVX40CT8NTE-KVeSFCg9vDGQ==@protonmail.com>
In-Reply-To: <F8KCTI206E.27CT1BTJ2NZKI@my.amazin.horse>
References: <2819882.8xdte9lYnu@esus> <94TsuhtP6GXVX2EUC8_FXEKKvVmGrIIeKcb286lH2gqkDZBBONDbyk8MyK_prHamSRKfb8lqMM6miq189Adpne3zt24wlfsRUR_36SZ5IS8=@protonmail.com> <F8KCTI206E.27CT1BTJ2NZKI@my.amazin.horse>
Feedback-ID: XShtE-_o2KLy9dSshc6ANALRnvTQ9U24aqXW2ympbGschdpHbU6GYCTUCtfmGhY9HmOyP1Uweyandwh1AVDFrQ==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="---------------------2df84fc201e66ca2bb6afa9f846f3b37"; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/IsJ7R31ovbcY1KXd_X6-lk657Nc>
Subject: Re: [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 19:05:07 -0000
Excellent, and we will certainly ping people here if we receive any compatibility complaints. -Bart ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, January 15, 2019 6:46 AM, Vincent Breitmoser <look@my.amazin.horse> wrote: > > > As discussed at the summit, Autocrypt and OpenKeychain will follow suit. > > See https://github.com/autocrypt/autocrypt/pull/393 > > - V > > Andre Heinecke aheinecke@gnupg.org wrote: > > > > Hi, > > On Tuesday, January 15, 2019 10:24:54 AM CET Sunny Rajan wrote: > > > > > 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! > > > > thumbs up I would turn the request around a bit. Please let us, or the > > OpenPGP Email list ( openpgp-email@enigmail.net ), know if you face interop or > > other problems. A status update in some months time which basically says "No > > Problems happened" would also be appreciated. > > I guess that there are some other implementations (me included) out there that > > think about taking the step to change the default. > > So congratulations for the courage to be on the forefront of progress. :-) > > Best Regards and I hope all goes well, > > Andre > > openpgp mailing list > openpgp@ietf.org > https://www.ietf.org/mailman/listinfo/openpgp
- Re: [openpgp] ProtonMail moving to default X25519… Bart Butler
- [openpgp] ProtonMail moving to default X25519 keys Sunny Rajan
- Re: [openpgp] ProtonMail moving to default X25519… Andre Heinecke
- Re: [openpgp] ProtonMail moving to default X25519… Vincent Breitmoser