[openpgp] Re: I-D Action: draft-ietf-openpgp-persistent-sy mmetric-keys-01.txt
Daniel Huigens <[email protected]>
| Newsgroups | gmane.ietf.openpgp |
|---|---|
| Message-ID | <Uw9c3PaYYP69Q-MnmFS-1GFB_EzAxcz2Wx3HwsBZoEGkUSMCcYmNi_PcSJf-k_1zrc0eWWsYJUN748YOZwbEko_YMvjX9rThYsdx1EkkFL4=@protonmail.com> |
Hi all,
I've finally published a new version of draft-ietf-openpgp-persistent-
symmetric-keys. Apologies it took so long.
Since we've last discussed the draft, I've reduced the number of
reserved code points for future persistent symmetric algorithms,
based on the feedback in the meeting.
The other concrete open question was whether it's necessary to be able
to derive the public key material from the private key material.
Before changing things back and potentially forth again, I wanted to
ask the working group whether it would be reasonable, in this case,
to require storing the public key fields together with the private key
(e.g. when storing the key in hardware, or some such)?
Note that the amount of data to store doesn't change, just whether that
data comes from the public key fields or the private key fields.
Note also that there are other existing algorithms where deriving the
public key material from the private key material isn't possible
(including ECDH and ECDSA), though for {X,Ed}{25519,448} it is
possible, which could be considered a nice property.
Anyway, let me know what you think, and whether you have any other
feedback, otherwise we can discuss it in the interim meeting :)
Best,
Daniel
_______________________________________________
openpgp mailing list -- [email protected]
To unsubscribe send an email to [email protected]