public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: robbat2@gentoo.org, "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-dev] [PATCH v4 08/14] glep-0063: Allow ECC curve 25519 keys
Date: Sat,  7 Jul 2018 07:56:17 +0200	[thread overview]
Message-ID: <20180707055623.28603-9-mgorny@gentoo.org> (raw)
In-Reply-To: <20180707055623.28603-1-mgorny@gentoo.org>

Optionally allow using ECC curve 25519 keys.  We already have
developers using those keys, and given that they are supported
by GnuPG 2.2, there's probably no reason to ban them.  However, they're
not recommended due to interoperability issues.
---
 glep-0063.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/glep-0063.rst b/glep-0063.rst
index b2e6679..472e540 100644
--- a/glep-0063.rst
+++ b/glep-0063.rst
@@ -34,6 +34,8 @@ v1.1
   The larger recommendation was unjustified and resulted in people
   unnecessarily replacing their RSA-2048 keys.
 
+  Minimal specification has been amended to allow for ECC keys.
+
 Motivation
 ==========
 
@@ -68,6 +70,8 @@ not be used to commit.
 
    b. RSA, >=2048 bits (OpenPGP v4 key format or later only)
 
+   c. ECC curve 25519
+
 4. Key expiry: 5 years maximum
 
 5. Upload your key to the SKS keyserver rotation before usage!
-- 
2.18.0



  parent reply	other threads:[~2018-07-07  6:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-07  5:56 [gentoo-dev] [PATCH v4 00/14] GLEP 63 update Michał Górny
2018-07-07  5:56 ` [gentoo-dev] [PATCH v4 01/14] glep-0063: Use 'OpenPGP' as appropriate Michał Górny
2018-07-07  5:56 ` [gentoo-dev] [PATCH v4 02/14] glep-0063: RSAv4 -> OpenPGP v4 key format Michał Górny
2018-07-07  5:56 ` [gentoo-dev] [PATCH v4 03/14] glep-0063: 'Gentoo subkey' → 'Signing subkey' Michał Górny
2018-07-07  5:56 ` [gentoo-dev] [PATCH v4 04/14] glep-0063: Root key → primary key Michał Górny
2018-07-07  5:56 ` [gentoo-dev] [PATCH v4 05/14] glep-0063: Split out the signing subkey into a separate point Michał Górny
2018-07-07  5:56 ` [gentoo-dev] [PATCH v4 06/14] glep-0063: Explain minimal & recommended sections Michał Górny
2018-07-07  5:56 ` [gentoo-dev] [PATCH v4 07/14] glep-0063: Change the recommended RSA key size to 2048 bits Michał Górny
2018-07-07  5:56 ` Michał Górny [this message]
2018-07-07  5:56 ` [gentoo-dev] [PATCH v4 09/14] glep-0063: Stop recommending DSA subkeys Michał Górny
2018-07-07  5:56 ` [gentoo-dev] [PATCH v4 10/14] glep-0063: Update and unify expiration term Michał Górny
2018-07-07  5:56 ` [gentoo-dev] [PATCH v4 11/14] glep-0063: Require renewal 2 weeks before expiration Michał Górny
2018-07-07  5:56 ` [gentoo-dev] [PATCH v4 12/14] glep-0063: Disallow using DSA keys Michał Górny
2018-07-07  5:56 ` [gentoo-dev] [PATCH v4 13/14] glep-0063: Remove whitespace from LDAP field Michał Górny
2018-07-07 12:27   ` Ulrich Mueller
2018-07-07 13:07     ` Michał Górny
2018-07-07  5:56 ` [gentoo-dev] [PATCH v4 14/14] glep-0063: Remove recommended gpg.conf Michał Górny
2018-07-07 12:17 ` [gentoo-dev] [PATCH v4 00/14] GLEP 63 update Ulrich Mueller
2018-07-07 13:11   ` Michał Górny
2018-07-07 14:20     ` Ulrich Mueller
2018-07-08 13:06     ` Kristian Fiskerstrand
2018-07-08 14:01       ` Michał Górny

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180707055623.28603-9-mgorny@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=robbat2@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox