[PR #268] [MERGED] Don't enable DNSSEC by default in -resolver. #1326

New issue

Closed

opened 2026-03-16 02:00:31 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 02:00:31 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hickory-dns/hickory-dns/pull/268
Author: @briansmith
Created: 10/26/2017
Status: ✅ Merged
Merged: 10/26/2017
Merged by: @bluejekyll

Base: master ← Head: no-default-dnssec

📝 Commits (2)

af6bfc4 Don't enable DNSSEC by default in -resolver.
4a22161 Merge branch 'master' into no-default-dnssec

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 resolver/Cargo.toml (+1 -1)

📄 Description

It is too easy for a library to accidentally add an OpenSSL dependency
through Trust-DNS by using Trust-DNS without disabling the default
features. This is especially bad because a library that hasn't
consciously chosen what to do about DNSSEC won't provide any APIs for
controlling if DNSSEC is used or how to configure its use (e.g.
configuring trust anchors).

The same applies to the ipconfig configure.

Resolve both by defaulting to not having these features.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/hickory-dns/hickory-dns/pull/268 **Author:** [@briansmith](https://github.com/briansmith) **Created:** 10/26/2017 **Status:** ✅ Merged **Merged:** 10/26/2017 **Merged by:** [@bluejekyll](https://github.com/bluejekyll) **Base:** `master` ← **Head:** `no-default-dnssec` --- ### 📝 Commits (2) - [`af6bfc4`](https://github.com/hickory-dns/hickory-dns/commit/af6bfc40550f8dc7571e4bd7cfb8d32261889c57) Don't enable DNSSEC by default in -resolver. - [`4a22161`](https://github.com/hickory-dns/hickory-dns/commit/4a2216161cfa77b68f40b6d1260ad3121c6dccd5) Merge branch 'master' into no-default-dnssec ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `resolver/Cargo.toml` (+1 -1) </details> ### 📄 Description It is too easy for a library to accidentally add an OpenSSL dependency through Trust-DNS by using Trust-DNS without disabling the default features. This is especially bad because a library that hasn't consciously chosen what to do about DNSSEC won't provide any APIs for controlling if DNSSEC is used or how to configure its use (e.g. configuring trust anchors). The same applies to the ipconfig configure. Resolve both by defaulting to not having these features. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>