getdns 1.5.2

This release has experimental support for GnuTLS >= 3.5.0 as replacement for OpenSSL.
To enabled, use the --with-gnutls option at configure time.
Note that getdns needs the gnutls-dane library too (which is used for SPKI authentication of DNS-over-TLS upstreams).
DNSSEC validation will use the cryptographic functions from libnettle (the cryptographic library also used by GnuTLS).

When build with GnuTLS, getdns will still be linked with libcrypto (from OpenSSL) for S/MIME verification of the root-anchors.xml file with Zero configuration DNSSEC.
It is our intention to replace that with something more GnuTLS native at some point in the future too, so that getdns can do without OpenSSL altogether.

Maintenance work included bringing TCP Fast Open up to par with current practice.
This means that at least on Linux 4.11+, getdns can connect TFO with TLS.

The most prominent bugfix is for DNSSEC scheduling which in some circumstances wrongly failed with insecure delegations of more than one label.

This release has the 0.2.6 release of Stubby included, with updates to documentation and fixes for the Windows build.

Milestone information

Project:
getdns
Series:
1.0
Version:
1.5.2
Released:
 
Registrant:
Peter J. Mello
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon getdns-1.5.2.tar.gz (md5) 10
last downloaded 47 weeks ago
Total downloads: 10

Release notes 

This release does not have release notes.

Changelog 

This release does not have a changelog.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.