support algorithm 16 (ed448) in DNSSEC
Recognising the increasing challenges in these times, would welcome the implementation of the Edwards-curve Digital Signature Algorithm (EdDSA) type ed448 for security and to keep ahead of the curve (sic.) on the cryptographic front...
interesting tool here too for those interested in checking out where they're up to with browser support (and to know the differences between the different algorithms): https://ed448.no/
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular. Everyone, please continue voting for this feature if you consider it important.
—
IG
-
John Scott commented
Yeah, I've noticed this too. On Parrot OS I was able to generate an ed448 pair and upload it as algorithm 16 for DNS settings on my company server. As you can see, the private key is even shorter than algorithms 13 and 14.
-----BEGIN PRIVATE KEY-----
MEcCAQAwBQYDK2VxBDsEOetJVU7BIj5oTyW5pMUWSiwkvbFA6GbeFrJg/EoKqSKh
Wg1PQXGb/agIcLBncrP5IQjFcebkTzIFJQ==
-----END PRIVATE KEY----- -
Anonymous commented
presumably this is going to have to happen anyway because otherwise Plesk will be not be a viable product in the market. These are already possible to generate on the Linux Command Line with SSL.