Skip to content

Releases: hickory-dns/hickory-dns

Upgrade *ring* to 0.9.x series

17 May 19:54
Compare
Choose a tag to compare

0.10.2

Fixed

Changed

  • Revamped signer and keypair to better deal with public key (possible breaking change)
  • Upgraded ring to 0.9.x series, requires pkcs8 for key storage
  • Dropped support for dangerous private key byte access (possible breaking change)
  • Upgraded tokio-rustls and rustls dependencies to support ring updates

Added

  • PublicKey and Verifier for verifying with zero copy from KEY and DNSKEY (possible breaking change)
  • Pkcs8 as a supported KeyFormat for storage (possible breaking change)

SIG0 fixed and validated with BIND

09 May 05:02
Compare
Choose a tag to compare

Two big changes in this release: rustls and native-tls have been released as separate crates. SIG0 has been fixed, there was a bug in the signing process.

0.10.1

Added

  • Added From<IpAddr> for Name (reverse DNS) #105
  • AppVeyor support #103
  • rustls client tls support (seperate crate)
  • full support for KEY RR in client
  • compatibility tests with BIND for SIG0 updates
  • Added full implementation of KEY type

Changed

  • Updated TLS documentation, added more elsewhere, docs required; fixes #102
  • Upgraded tokio-core and moved to tokio-io
  • Important Some Server types have been migrated to RFC#344 style. get_field() -> field(); field() -> set_field()
  • Moved native-tls client impl to seperate crate
  • Defaulted to OpenSSL for tls implementation

Fixed

  • key_tag calculation for DNSKEY and KEY now correct #118 (@jannic)
  • SIG0 signing fixed to match RFC and BIND #120 (@jannic)

DNS over TLS

10 Mar 07:23
Compare
Choose a tag to compare

0.10.0

Changed

  • Important Possible breaking API change, the original Client has been renamed
    In an attempt to reduce the overhead of managing the project. The original
    Client has now been revamped to essentially be a synchronous Client over the
    ClientFuture implementation. The ClientFuture has proven to be a more stable
    and reliable implementation. It was attempted to make the move seamless,
    but two new types were introduced, SyncClient and SecureSyncClient, which
    are both synchronous implementations of the old Client function interfaces.
    Please read those docs on those new types and the Client trait.
  • When EDNS option is present, return only the digest understood matching RRSETs
  • All code reformatted with rustfmt
  • Important breaking change, all Record and associated types have been migrated to RFC#344 style. get_field() -> field(); field() -> set_field()

Removed

  • Important The original Server implementation was removed entirely. Please
    use the ServerFuture implementation from now on. Sorry for the inconvenience,
    but this is necessary to make sure that the software remains at a high quality
    and there is no easy way to migrate the original Server to use ServerFuture.

Added

  • Initial support for ECDSAP256SHA256, ECDSAP384SHA384 and ED25519 (client and server)
  • additional config options for keys to named, see tests/named_test_configs/example.toml
  • Added DNS over TLS support, RFC 7858, #38
  • Added native-tls with support for macOS and Linux (DNS over TLS)
  • matrixed tests for all features to Travis

Update rust-openssl to 0.9 series

31 Dec 21:28
Compare
Choose a tag to compare

0.9.3

Changed

  • updated to rust-openssl 0.9.x series
  • restructured dnssec code to better support alternate key formats

Direct dependency on MIO now optional

21 Dec 16:39
Compare
Choose a tag to compare

0.9.2

Changed

  • mio_client is now an optional feature in favor of the futures-rs ClientFuture

OpenSSL now optional

21 Dec 16:09
Compare
Choose a tag to compare

0.9.1

Changed

  • OpenSSL is now an optional feature for the client

ServerFuture and split crates

17 Dec 08:28
Compare
Choose a tag to compare

Added

  • new ServerFuture tokio and futures based server, #61
  • UdpStream & TcpSteam to support stream of messages with src address
  • TimeoutStream to wrap TcpStreams to help guard against malicious clients
  • Added Notify support to ClientFuture
  • Added IntoRecordSet and conversion impls for RecordSet and Record

Changed

  • Split Server and Client into separate crates, #43
  • Moved many integration tests to tests from src, #52
  • Migrated all handles to new futures::sync::mpsc impls
  • Modified all requisite client methods for IntoRecordSet.
  • All client methods now support multiple records per query, update, notify and delete

Fixed

  • Flush TcpStream after fully sending Message
  • Recognize no bytes read as closed TcpStream

Fix compilation on rustc 1.11

04 Nov 02:50
Compare
Choose a tag to compare

Fixed

  • Fix build on rustc 1.11, #66

ClientFuture

03 Nov 07:19
Compare
Choose a tag to compare

Added

  • SecureClientHandle, for future based DNSSec validation.
  • ClientFuture, futures based client implementation, #32

Fixed

  • Randomized ports for client connections and message ids, #23
  • OpCode::From for u8 removed, added OpCode::from_u8(), #36
  • Fix for named startup related to ipv6, #56

Changed

  • Upgraded OpenSSL to 0.8.* #50
  • Cleaned up the Server implementation to isolate connection handlers
  • Deprecated old Client will possibly remove in the future