From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: robbat2@gentoo.org
Subject: Re: [gentoo-dev] [PATCH 5/4] glep-0063: Allow ECC keys
Date: Wed, 04 Jul 2018 09:54:17 +0200 [thread overview]
Message-ID: <1530690857.914.18.camel@gentoo.org> (raw)
In-Reply-To: <751a88c0-e367-4394-825e-baba66c95fb6@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
W dniu śro, 04.07.2018 o godzinie 09∶49 +0200, użytkownik Kristian
Fiskerstrand napisał:
> On 07/04/2018 09:22 AM, Michał Górny wrote:
> > + c. ECC
>
> Likely should not blanket accept ECC for various reasons. For one thing
> the curves we likely would want to accept are not standardized, so you
> have interoperability issues.
>
> The hardware situation is improving somewhat on these, so that is less
> of a concern now than back in the day.
>
> But there aren't really very strong arguments in favor of ecc, and in
> the case of quantum computation there less protection offered from ecc
> due to smaller key sizes.
>
> We also keep gnupg 1.4 in tree that does not, and will not, support ecc.
Well, we have developers using ECC (Curve 25519, to be specific).
I don't really know enough about this to judge but we either need to
allow at least this, or convince those devs to change to RSA.
Would one of the following wordings be better:
a) ECC, Curve 25519[, ...]
b) ECC, curves supported by GnuPG version ...
Alternatively, do you have other suggestions?
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2018-07-04 7:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 13:29 [gentoo-dev] [PATCH 0/4] GLEP 63: clean up, and reduce key size to RSA-2048 Michał Górny
2018-07-03 13:29 ` [gentoo-dev] [PATCH 1/4] glep-0063: Use 'OpenPGP' as appropriate Michał Górny
2018-07-03 13:29 ` [gentoo-dev] [PATCH 2/4] glep-0063: RSAv4 -> OpenPGP v4 key format Michał Górny
2018-07-03 13:29 ` [gentoo-dev] [PATCH 3/4] glep-0063: Clarify dedicated signing subkey in minimal reqs Michał Górny
2018-07-03 13:29 ` [gentoo-dev] [PATCH 4/4] glep-0063: Change the recommended RSA key size to 2048 bits Michał Górny
2018-07-03 16:40 ` [gentoo-dev] [PATCH 0/4] GLEP 63: clean up, and reduce key size to RSA-2048 Aaron Bauman
2018-07-03 16:42 ` Aaron Bauman
2018-07-03 19:55 ` Michał Górny
2018-07-04 7:22 ` [gentoo-dev] [PATCH 5/4] glep-0063: Allow ECC keys Michał Górny
2018-07-04 7:49 ` Kristian Fiskerstrand
2018-07-04 7:54 ` Michał Górny [this message]
2018-07-04 8:01 ` Kristian Fiskerstrand
2018-07-04 8:42 ` Michał Górny
2018-07-04 8:51 ` Kristian Fiskerstrand
2018-07-04 9:09 ` Michał Górny
2018-07-04 9:49 ` Kristian Fiskerstrand
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=1530690857.914.18.camel@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