Canonical Key Format for ECC?
Daniel Kahn Gillmor
dkg at fifthhorseman.net
Wed Jun 3 17:03:13 CEST 2015
On Wed 2015-06-03 07:49:14 -0400, NIIBE Yutaka wrote:
> Then, the private key is created under
> .gnupg/private-keys-v1.d/E4403F3FD7A443FAC29FEF288FA0D20AC212851E.key
> in the format of:
>
> (private-key(ecc(curve 1.2.840.10045.3.1.7)....))
>
> On the other hand, when we generate a key, it is in the format of:
>
> (private-key(ecc(curve NIST P-256)...))
>
> Those two are same thing, but I think that it's better to use one.
>
> Shouldn't we fix the code (g10/import.c:transfer_secret_keys) to use
> the name of curve (instead of OID string)?
I like the named format better than the OID format, just because it's
more readable if someone looks in. I don't know anyone who has
memorized the OID space, but i know that the string "NIST P-256" is
meaningful to many of the people who might dig around inside
~/.gnupg/private-keys-v1.d.
--dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 948 bytes
Desc: not available
URL: </pipermail/attachments/20150603/d57118e7/attachment.sig>
More information about the Gnupg-devel
mailing list