RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
RFC 8624 [1] mandates DSA to be not used for validation. More recent versions disable it in the code, for example RHEL9. But it would not be wrong to add also NSEC3 variant of DSA.

Version-Release number of selected component (if applicable):
crypto-policies-20211116-1.gitae470d6.el8.noarch
bind-9.11.36-3.el8.x86_64


How reproducible:
reliable

Steps to Reproduce:
1. systemctl restart named
2. (add forwarders { 8.8.8.8; }; to options {} in /etc/named.conf if needed)
3. dig @localhost secure.d2a6n3.rootcanary.net. | grep flags:
4. dig @localhost secure.d2a3n1.rootcanary.net. | grep flags:

Actual results:
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
; EDNS: version: 0, flags: do; udp: 1232
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
; EDNS: version: 0, flags: do; udp: 1232


Expected results:
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
; EDNS: version: 0, flags: do; udp: 1232
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
; EDNS: version: 0, flags: do; udp: 1232


Additional info:
AD flag has to be removed.

1. https://datatracker.ietf.org/doc/html/rfc8624#section-3.1

Related unbound bug #2071968, which should ensure similar thing in unbound.

It is not necessary for bind 9.16.x, because it disables those algorithms directly by code. But that code-policy snippet makes it more obvious even on RHEL9 and Fedora. It would not be wrong, if it contained this on all versions:

disable-algorithms "." {
RSAMD5;
DSA;
NSEC3DSA;
};
disable-ds-digests "." {
GOST;
};

Might have mentioned target file path: /etc/crypto-policies/back-ends/bind.config

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (crypto-policies bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:3025