trust-dns

Apart from the difference in programming language, how does this compare to https://github.com/bluejekyll/trust-dns ?

For reference, what I have used that makes me claim this without being misleading (not necessarily all at the same time): https://rocket.rs/, https://rusoto.github.io/rusoto/rusoto_core/index.html, https://docs.rs/postgres/0.15.1/postgres/, https://docs.rs/kafka/0.7.0/kafka/, https://docs.rs/reqwest/0.8.1/reqwest/, as well as many other supporting libraries. I've not run into many things where there isn't already support. Also, in terms of networking, if your doing blocking IO, the stdlib is fine. Otherwise, from my experience, I really like https://tokio.rs/ for non-blocking (I know people are torn on this one) and have used it in my DNS impl, https://github.com/bluejekyll/trust-dns For more info on web and Rust, this is a great page: http://www.arewewebyet.org/

I’ve been working on https://github.com/bluejekyll/trust-dns for a bit over two years now. About a year ago a new contributor added Windows build support and testing with AppVeyor, which was awesome. Originally I started this project more for server side stuff, but recently have been very focused on a full resolver which could be used as a replacement for the OS system resolver. A question for HN, what would you like to see in this context that would make a replacement resolver on Windows something you’d use? To be clear, it’s not something you could use dropin right now, it can only be used as an internal library to Rust at-the-moment, but I’ve been planning to start working on a daemon that could act as a caching system resolver in the next little bit.

The Client/Resolver doesn't actually have a config for enabling TLS ATM, this should be added as a backlog issue. At the moment you'd have to build this into a custom Rust impl. I've been considering whether it can be an addition to the resolv.conf, or should just have a separate TOML. If you don't mind, would you want to file an issue and describe how you want to use this? Edit: I have been planning on a system daemon caching resolver that can be run on any OS. This work is only just getting started. > In a couple places, 'Ellyptic' was written Yeah, me and spelling have had a issue going all the way back to 1st grade ;) Edit: btw, you're comment about CN got me thinking again about the correct usage of that, and I wonder if "name" is even correct. It might be better to have the certs be validated against IP's listed in the Subject of t

A little Self promotion: TRust-DNS Resolver and Client support ED25519. Currently working through some issues on the signing logic in the Authority. https://github.com/bluejekyll/trust-dns

Some of my favorite examples: https://os.phil-opp.com https://github.com/helena-project/tock https://www.redox-os.org https://github.com/redox-os/tfs https://github.com/intermezzOS/kernel The biggest application example: https://github.com/servo/servo And some self promotion: https://github.com/bluejekyll/trust-dns ---- I encourage all programmers to check it out. You may discover like me, that Rust is a compiler and language which guards against all the hard learned lessons I've had over my career. It's an amazing language to program in.

This is something djbdns excelled at in it's initial implementation. DJB, always impressive. These vulnerabilities don't seem all that hard to fix. This also points out why DNSSec is so important IMO. I know many don't see as much value in it, but it can be very useful for defending against inauthentic records. It's a big reason why I've been working on TRust-DNS. On a separate note; I'd love feedback on these areas of my code if anyone would care to... In TRust-DNS, at least to my best ability, I implemented them in these two locations: randomized port (UDP only): https://github.com/bluejekyll/trust-dns/blob/master/client/s... randomized msg id (TCP & UDP): https://github.com/bluejekyll/trust-dns/blob/master/client/s...