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.
Bug 2079548 - [unbound: FIPS mode] does not resolve ED25519 and ED448
Summary: [unbound: FIPS mode] does not resolve ED25519 and ED448
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2022-05-23
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: unbound
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Menšík
QA Contact: Petr Sklenar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-27 18:44 UTC by Petr Menšík
Modified: 2022-11-15 11:10 UTC (History)
1 user (show)

Fixed In Version: unbound-1.16.0-3.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 10:15:56 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github NLnetLabs unbound pull 671 0 None Merged Disable ED25519 and ED448 in FIPS mode on openssl3 2022-07-07 11:07:02 UTC
Gitlab redhat/centos-stream/rpms unbound merge_requests 15 0 None merged Disable ED25519 and ED448 in FIPS mode 2022-07-08 18:27:47 UTC
Red Hat Issue Tracker RHELPLAN-120254 0 None None None 2022-04-27 18:50:24 UTC
Red Hat Product Errata RHSA-2022:8062 0 None None None 2022-11-15 10:16:20 UTC

Description Petr Menšík 2022-04-27 18:44:13 UTC 
Description of problem:
Similar to bug #2077889 for bind, unbound also does not pass validation of ED25519 and ED448 algorithms 

Version-Release number of selected component (if applicable):
unbound-1.13.1-13.el9_0.x86_64

How reproducible:
reliable

Steps to Reproduce:
1. fips-mode-setup --enable && reboot
2. unbound-host -rvD secure.d4a16n3.rootcanary.net.
3.

Actual results:
secure.d4a16n3.rootcanary.net. has address 145.97.20.20
validation failure <secure.d4a16n3.rootcanary.net. A IN>: use of key for crypto failed from 10.2.32.1 for key d4a16n3.rootcanary.net. while building chain of trust
secure.d4a16n3.rootcanary.net. has IPv6 address 2001:610:188:408::20
validation failure <secure.d4a16n3.rootcanary.net. AAAA IN>: key for validation d4a16n3.rootcanary.net. is marked as invalid because of a previous validation failure <secure.d4a16n3.rootcanary.net. A IN>: use of key for crypto failed from 10.2.32.1 for key d4a16n3.rootcanary.net. while building chain of trust
validation failure <secure.d4a16n3.rootcanary.net. MX IN>: key for validation d4a16n3.rootcanary.net. is marked as invalid because of a previous validation failure <secure.d4a16n3.rootcanary.net. A IN>: use of key for crypto failed from 10.2.32.1 for key d4a16n3.rootcanary.net. while building chain of trust


Expected results:
secure.d4a16n3.rootcanary.net. has address 145.97.20.20 (insecure)
secure.d4a16n3.rootcanary.net. has IPv6 address 2001:610:188:408::20 (insecure)
secure.d4a16n3.rootcanary.net. has no mail handler record (insecure)



Additional info:
This check might need eventually removed, once those algorithms are approved to FIPS.
Comment 6 Petr Menšík 2022-07-07 11:04:32 UTC 
Finally merged by upstream without modification.
Comment 7 Petr Menšík 2022-07-08 18:07:47 UTC 
Prepared pull request
Comment 17 errata-xmlrpc 2022-11-15 10:15:56 UTC 
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 (Moderate: unbound security, 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/RHSA-2022:8062
Note You need to log in before you can comment on or make changes to this bug.