mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[GH-ISSUE #38] Feature request: RFC 7858, DNS over TLS #26
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @farrokhi on GitHub (Aug 22, 2016).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/38
I just finished reading your article about this implementation and noticed that you are working on DNSCrypt integration. I thought maybe it would be a better idea to be the first project to put support for RFC 7858 (DNS over TLS) in a production grade client/server.
@bluejekyll commented on GitHub (Aug 22, 2016):
I was looking at that. It looks like it would definitely be capable of covering the same use case. I definitely have some issues with DNSCrypt, what I like about this is I can make use of more off-the-shelf tools.
One advantage of DNSCrypt is that it supports UDP. It looks like the UDP portion of DNSoD is still in draft form, but making progress.
Maybe this would be a good thing to target. I'll look into it.
@bluejekyll commented on GitHub (Jan 17, 2017):
FYI, working on this now. It shouldn't be difficult to get this done client side, server side will take longer to get proper configs ready.
@bluejekyll commented on GitHub (Jan 23, 2017):
End-to-end TLS done. I added some ease of use stuff to the
rust-openssllibrary, going to wait to see if that is accepted. I can continue on with integrating into the server configuration. Progress can be tracked in https://github.com/bluejekyll/trust-dns/tree/dns_over_tlsThere will probably need to be some updates made to
native-tisfor the server side, so this change may be dependent on multiple upstream libraries, which means merging into master is still a little off.@bluejekyll commented on GitHub (Feb 5, 2017):
Just pushed server side implementations. Tests are forth-coming.
If anyone would care to review, I'd definitely appreciate it.
@bluejekyll commented on GitHub (Feb 7, 2017):
macOS support is done through the use of native-tls, and security-framework. I still need to get Linux support done, which requires an abstraction over some of the certificates on the client and server side.
@bluejekyll commented on GitHub (Feb 12, 2017):
I've run into some issues on the Linux side. If anyone is interested in helping me figure this out, that would be awesome:
https://github.com/sfackler/rust-native-tls/issues/20
@bluejekyll commented on GitHub (Feb 15, 2017):
Ok, fixed in the rust-openssl library: https://github.com/sfackler/rust-openssl/pull/582
@bluejekyll commented on GitHub (Feb 25, 2017):
landed in master... I'll be working on a 0.10.0 release.