[GH-ISSUE #60] Implement draft-ietf-curdle-dnskey-eddsa (EdDSA signatures for DNS) #38

Closed
opened 2026-03-07 22:18:14 +03:00 by kerem · 4 comments
Owner

Originally created by @briansmith on GitHub (Nov 1, 2016).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/60

See draft-ietf-curdle-dnskey-eddsa.

Originally created by @briansmith on GitHub (Nov 1, 2016). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/60 See [draft-ietf-curdle-dnskey-eddsa](https://tools.ietf.org/html/draft-ietf-curdle-dnskey-eddsa).
kerem 2026-03-07 22:18:14 +03:00
Author
Owner

@bluejekyll commented on GitHub (Nov 2, 2016):

Sweet. We can do this after switching to ring

<!-- gh-comment-id:257765113 --> @bluejekyll commented on GitHub (Nov 2, 2016): Sweet. We can do this after switching to _ring_
Author
Owner

@bluejekyll commented on GitHub (Dec 31, 2016):

I added a new KeyPair type to the client library. This allows for a high level abstraction over different key implementations. We should be able to use it to abstract over different implementations. So adding I looked briefly at rings eddsa and I think it should be easily integrated.

<!-- gh-comment-id:269882828 --> @bluejekyll commented on GitHub (Dec 31, 2016): I added a new KeyPair type to the client library. This allows for a high level abstraction over different key implementations. We should be able to use it to abstract over different implementations. So adding I looked briefly at rings eddsa and I think it should be easily integrated.
Author
Owner

@bluejekyll commented on GitHub (Jan 1, 2017):

@briansmith if you get a chance, can you look at my diff that I just posted? I want to make sure that all that looks legit to you...

<!-- gh-comment-id:269897263 --> @bluejekyll commented on GitHub (Jan 1, 2017): @briansmith if you get a chance, can you look at my diff that I just posted? I want to make sure that all that looks legit to you...
Author
Owner

@bluejekyll commented on GitHub (Jan 10, 2017):

FYI, I just landed this in main, I'll close this here, though I should probably mark this as experimental until there is external validation.

<!-- gh-comment-id:271510796 --> @bluejekyll commented on GitHub (Jan 10, 2017): FYI, I just landed this in main, I'll close this here, though I should probably mark this as experimental until there is external validation.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hickory-dns#38
No description provided.