This repository has been archived by the owner on Sep 27, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 512
DNSSEC: ECDSA support (Cloudflare, 1984.is, etc.) #357
Comments
+1, as this issue still exists almost a year later. From the blog post announcing this feature in 2018:
Is there any progress on this feature? |
Hi, I am suffering from this problem too. I would like to use AWS Route 53 for DNS, and their implementation is using ECDSA. I would like this to be supported. Thank you! |
I would also like to have this. |
u would like to have what
…On Mon, 11 Apr 2022, 13:46 Aleš Ferlan, ***@***.***> wrote:
I would also like to have this.
—
Reply to this email directly, view it on GitHub
<#357 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHMUVGOCRFZCYNXDTSKECG3VEQGIBANCNFSM4N4VP3ZQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
the thing that this issue is about |
This was referenced May 10, 2022
It appears that the implementation is currently under audit. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have read about the .xyz support for ENS, but also read that ECDSA signature is not supported for DNSSEC yet, meaning most current, up-to-date providers like Cloudflare, 1984.is are unlucky.
Could you please add support for this modern, smaller, faster signature?
The text was updated successfully, but these errors were encountered: