This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2077906 - [bind: FIPS mode] Resolution of many domains signed by just 1024 bit key would start failing
Summary: [bind: FIPS mode] Resolution of many domains signed by just 1024 bit key woul...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: bind
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Petr Menšík
QA Contact: rhel-cs-infra-services-qe
URL:
Whiteboard:
Depends On: 2077884
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-22 14:43 UTC by Petr Menšík
Modified: 2023-09-21 17:55 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-21 17:55:27 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Internet Systems Consortium (ISC) isc-projects bind9 merge_requests 6238 0 None opened Draft: Introduce few FIPS mode checks 2022-04-29 20:45:31 UTC
Red Hat Issue Tracker   RHEL-6447 0 None Migrated None 2023-09-21 17:55:23 UTC
Red Hat Issue Tracker RHELPLAN-119705 0 None None None 2022-04-22 14:48:07 UTC

Description Petr Menšík 2022-04-22 14:43:42 UTC 
Description of problem:
Many DNSSEC ZSK keys used on public zones use short keys. Those short keys verifications works on RHEL 9.0 at the moment, but is going to be fixed by bug #2077884.

Version-Release number of selected component (if applicable):
bind-9.16.23-1.el9.x86_64

How reproducible:
would be reliable


Steps to Reproduce:
1. kdig +multi -t dnskey 100.in-addr.arpa | grep '1[0-9]\{3\}b'
2. fips-mode-setup --enable && reboot
3. systemctl restart named

Actual results:
; <<>> DiG 9.16.23-RH <<>> @localhost 100.in-addr.arpa
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 51523
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0


Expected results:
dig @localhost 100.in-addr.arpa

; <<>> DiG 9.16.23-RH <<>> @localhost 100.in-addr.arpa
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51523
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: ccbd17067595b02d010000006262bec84c89c72cc8cf6a3d (good)
;; QUESTION SECTION:
;100.in-addr.arpa.		IN	A

;; AUTHORITY SECTION:
100.in-addr.arpa.	10765	IN	SOA	z.arin.net. dns-ops.arin.net. 2017033603 1800 900 691200 10800

;; Query time: 1 msec
;; SERVER: ::1#53(::1)
;; WHEN: Fri Apr 22 10:42:16 EDT 2022
;; MSG SIZE  rcvd: 127


Additional info:
Comment 1 Petr Menšík 2022-04-25 09:47:30 UTC 
Sent notification and question to IETF dnsop group [1]. Also to bind users [2].

1. https://mailarchive.ietf.org/arch/msg/dnsop/Vk0tdPPmwgRJA6Hy-3ykIHB_-l8/
2. https://lists.isc.org/pipermail/bind-users/2022-April/105981.html
Comment 2 Petr Menšík 2022-04-29 20:45:31 UTC 
First proposal sent to upstream, but it does not work at all. It breaks resolution and security flags, but result is not converted to insecure this way. Going to be much harder it seems.

Anywhere in code when availability of algorithm is tested, the used key is not yet loaded. Converting bitsize of key to have idea is not so easy.
Comment 3 RHEL Program Management 2023-09-21 17:51:35 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 4 RHEL Program Management 2023-09-21 17:55:27 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.