Timeline for Converting a C25519 curve into a NIST-supported curve for FIPS crypto
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 21, 2017 at 14:39 | comment | added | Adam Ierymenko | It would also make the upgrade deterministic, which is good in some contexts. | |
| Aug 21, 2017 at 14:38 | vote | accept | Adam Ierymenko | ||
| Jul 25, 2017 at 8:15 | comment | added | rmalayter | @fgrieu They could of course certify these new keys using their Curve25519 keys just as in your answer. The point of this deterministic approach is that they don't need to store and manage a new keypair. | |
| Jul 25, 2017 at 6:33 | comment | added | fgrieu♦ | Yes, that can be done, and can be useful if short on entropy. But that way of generating the new NIST key pair won't solve the issue that the other party has no trust in the newly generated public key. | |
| Jul 24, 2017 at 22:38 | history | edited | rmalayter | CC BY-SA 3.0 |
added 2 characters in body; added 8 characters in body
|
| Jul 24, 2017 at 22:25 | history | edited | rmalayter | CC BY-SA 3.0 |
added 21 characters in body
|
| Jul 24, 2017 at 22:19 | history | answered | rmalayter | CC BY-SA 3.0 |