Bump hickory-proto from 0.24.1 to 0.24.4

[dependabot]

Bumps hickory-proto from 0.24.1 to 0.24.4.

Release notes

Sourced from hickory-proto's releases.

0.24.4

What's Changed

• [0.24] Use cargo environment variables for path to executable by @​msrd0 in hickory-dns/hickory-dns#2773
• [0.24] bump ring to 0.17.8 by @​drahnr in hickory-dns/hickory-dns#2759
• Prepare 0.24.4 by @​djc in hickory-dns/hickory-dns#2784

v0.24.3

What's Changed

• Fix tests on 0.24 release branch by @​divergentdave in hickory-dns/hickory-dns#2752

Full Changelog: hickory-dns/hickory-dns@v0.24.2...v0.24.3

v0.24.2

What's Changed

• 0.24: upgrade to idna 1 by @​djc in hickory-dns/hickory-dns#2664

Changelog

Sourced from hickory-proto's changelog.

Change Log: Hickory DNS (formerly, Trust-DNS)

All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning.

All notes should be prepended with the location of the change, e.g. (proto) or (resolver).

0.25.0

0.25.0 represents a large release for the Hickory DNS project. Over 14 months since 0.24.0, we've added two new maintainers, divergentdave and marcus0x62, and have addressed many limitations. A team from Ferrous Systems shored up our support for DNSSEC, and we addressed a number of findings from our first security audit.

Breaking changes

This is not an exhaustive list of changes, but here are some of the most impactful breaking changes in this release:

• Configuration for the Hickory DNS server crate has been reworked substantially to be more robust and secure. Most of the code related to the server binary has been moved out of the hickory-server library and into the hickory-dns binary crate.
• The synchronous API, which previously provided a thin partial wrapper over the asynchronous API, has been removed. Downstream users will have to migrate to the asynchronous API.
• Support for TLS using native-tls or OpenSSL has been removed. We now only provide first-party support for rustls (0.23, for DNS over TLS, HTTP/2, QUIC and HTTP/3). We support ring or aws-lc-rs for cryptographic operations both for DNSSEC and TLS. The dns-over-rustls,dns-over-native-tls, dns-over-openssl, dns-over-https-rustls, dns-over-https, dns-over-quic and dns-over-h3 features have been removed in favor of a set of {tls,https,quic,h3}-{aws-lc-rs,ring} features across our library crates.
• The async-std-resolver crate has been removed. Support for the async-std runtime has been subsumed into the hickory-resolver crate.
• The DNSSEC API was reworked to extend coverage to the recursor, add support for NSEC3, and make the API more ergonomic and harder to misuse.
• Moved the RuntimeProvider API into the proto crate and use it consistently across the project.
• Name values are now rooted by default in many places, and more consistently maintain their fqdn status.
• Error types are now exposed directly in the crate roots.
• Top-level TLS configuration in the resolver crate has moved to the ResolverOpts type. Specific NameServerConfigs should implicitly set up the ALPN protocol appropriate for the DNS protocol.
• The ResolverOptions fields authentic_data and shuffle_dns_servers were removed. The former field didn't do anything; and should be covered by new DNSSEC API. shuffle_dns_servers functionality has been subsumed into the server_ordering_strategy field.
• The use of rustls-native-certs via the native-certs feature was replaced with rustls-platform-verifier.
• The tokio-runtime feature was renamed to tokio.
• The serde-config feature was renamed to serde.
• Serializations (and what the new release can deserialize) has changed; data serialized by 0.24 may not deserialize correctly on 0.25, and vice versa.

... (truncated)

Commits

• b00cc10 Bump versions to 0.24.4
• 653d03e fix/test: use .1 ending of IP address in test, .0 will yield a different error
• 5a5c981 feat: add err log if not matching the expected kind
• 321d53f chore/dependency(ring): bump to 0.17.8
• 39bf9c8 [0.24] Use cargo environment variables for path to executable (#2773)
• 7df98a4 Fix tests on 0.24 release branch (#2752)
• fd25a74 Bump version to 0.24.3
• e118c6e Check RRSIG over DNSKEY RRset w/ authenticated key
• 9cdb484 Bump version to 0.24.2
• 1b84e3a Upgrade h3 and h3-quinn to avoid instant
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}