Timeline for gpg key size of 4096 and "the future is ECC"
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 4, 2023 at 11:17 | comment | added | Thomas Guyot-Sionnest | @ARGYROUMINAS So what is your question exactly? ECC is still not supported by older tools, not officially standardized (subject to changes) and is still a new technology that hasn't been tested as much as classic crypto. You can use it if you want but for best compatibility RSA is still a very well trusted crypto. | |
| Jul 3, 2023 at 4:56 | comment | added | ARGYROU MINAS | @ThomasGuyot-Sionnest What does the fact that the RFC4880bis is still a draft and not approved mean, based on your take on it? GnuPG already uses those curves and RFC4880bis can be enabled. | |
| Jul 8, 2021 at 4:28 | comment | added | Thomas Guyot-Sionnest | For compatibility with older systems you should stick with RSA. If unsure about the key size, IMHO just pick the largest as you won't notice the difference. For ECC I would at least recommend waiting for the RFC's to be published, see: wiki.gnupg.org/ECC. This opens up a whole lot of new questions though, with ECC there's some mistrust in curves like the NIST ones with no rationale behind some of the chosen parameters. GnuPG plans on using Curve25519 by default, and although SSH requires support for NIST curves it prefers Curve25519 or its close variant, Ed25519, when possible. | |
| May 7, 2020 at 21:29 | vote | accept | unsafe_where_true | ||
| May 7, 2020 at 21:25 | history | edited | Hubert Jasieniecki | CC BY-SA 4.0 |
Add more content to fully answer the question.
|
| May 7, 2020 at 21:15 | review | First posts | |||
| May 7, 2020 at 22:14 | |||||
| May 7, 2020 at 21:12 | history | answered | Hubert Jasieniecki | CC BY-SA 4.0 |