This project has moved and is read-only. For the latest updates, please go here.

Decouple DANE and DNS

Oct 16, 2015 at 9:57 AM
Edited Oct 16, 2015 at 11:58 AM

it would be great if you could decouple all the DANE stuff from the rest of the library. This would remove the dependency to BouncyCastle from the library - which is awesome, by the way :-)
Oct 28, 2015 at 8:56 AM

BouncyCastle is not only used in the DANE stuff, it is used for more or less all cryptographic stuff of the DNSSEC classes. And splitting the DNS and DNSSEC classes would be very tricky.

Because of that: Sorry, you have to live with the dependency.
Oct 22, 2016 at 11:03 AM
Edited Oct 22, 2016 at 11:04 AM
@hkrause: Using BouncyCastle is wise - The .NET Framework built-In encryption classes are not very cross-platform, nor very good and easy to use, plus you never know when they're calling the WinCrypt-API, which is NSA-backdoored.
And BouncyCastle is an excellent library, fully-managed code, backwards-compatible to .NET 2.0, and forward compatible to .NET Core already, wouldn't know why you wouldn't want to have it in there.