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 1484264 - Corosync hangs on secauth with FIPS enabled [rhel-7.4.z]
Summary: Corosync hangs on secauth with FIPS enabled [rhel-7.4.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: corosync
Version: 7.4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Jan Friesse
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1461450
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-23 07:20 UTC by Oneata Mircea Teodor
Modified: 2017-09-05 11:24 UTC (History)
10 users (show)

Fixed In Version: corosync-2.4.0-9.el7_4.2
Doc Type: Bug Fix
Doc Text:
Previously, when the corosync service had encryption enabled and was running in an environment with FIPS kernel mode activated, corosync terminated unexpectedly after starting. A patch has been applied to load a symmetric key that works when FIPS kernel mode is activated, and the described problem no longer occurs.
Clone Of: 1461450
Environment:
Last Closed: 2017-09-05 11:24:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
7.4.z-bz1484264-1-totem-Propagate-totem-initialization-failure (2.93 KB, patch)
2017-08-24 07:58 UTC, Jan Friesse 		no flags Details | Diff
7.4.z-bz1484264-2-totemcrypto-Refactor-symmetric-key-importing (4.56 KB, patch)
2017-08-24 07:58 UTC, Jan Friesse 		no flags Details | Diff
7.4.z-bz1484264-3-totemcrypto-Use-different-method-to-import-key (5.51 KB, patch)
2017-08-24 07:58 UTC, Jan Friesse 		no flags Details | Diff
7.4.z-bz1484264-4-totemcrypto-Fix-compiler-warning (1.63 KB, patch)
2017-08-24 07:59 UTC, Jan Friesse 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2570 0 normal SHIPPED_LIVE corosync bug fix update 2017-09-05 15:17:18 UTC

Description Oneata Mircea Teodor 2017-08-23 07:20:18 UTC 
This bug has been copied from bug #1461450 and has been proposed to be backported to 7.4 z-stream (EUS).
Comment 2 Jan Friesse 2017-08-24 07:58:44 UTC 
Created attachment 1317477 [details]
7.4.z-bz1484264-1-totem-Propagate-totem-initialization-failure

totem: Propagate totem initialization failure

(backported from master 564b4bf7d4c5b3f632a48610761dce58e5809b3a)

Signed-off-by: Jan Friesse <jfriesse>
Reviewed-by: Christine Caulfield <ccaulfie>
Comment 3 Jan Friesse 2017-08-24 07:58:50 UTC 
Created attachment 1317478 [details]
7.4.z-bz1484264-2-totemcrypto-Refactor-symmetric-key-importing

totemcrypto: Refactor symmetric key importing

Signed-off-by: Jan Friesse <jfriesse>
Reviewed-by: Fabio M. Di Nitto <fdinitto>
Reviewed-by: Christine Caulfield <ccaulfie>
Comment 4 Jan Friesse 2017-08-24 07:58:57 UTC 
Created attachment 1317479 [details]
7.4.z-bz1484264-3-totemcrypto-Use-different-method-to-import-key

totemcrypto: Use different method to import key

PK11_ImportSymKey doesn't work when FIPS is enabled because NSS is
targeting to FIPS Level 2 where loading of unencrypted symmetric
key is prohibited.

FIPS Level 2 is hard to achieve without breaking compatibility so patch
implements "workaround" to make NSS behave like FIPS Level 1
(where is allowed to load unencrypted symmetric key).

Workaround is about using temporal key to encrypt corosync authkey in
memory and then to unwrap it into valid NSS key.

Signed-off-by: Jan Friesse <jfriesse>
Reviewed-by: Fabio M. Di Nitto <fdinitto>
Reviewed-by: Christine Caulfield <ccaulfie>
Comment 5 Jan Friesse 2017-08-24 07:59:02 UTC 
Created attachment 1317480 [details]
7.4.z-bz1484264-4-totemcrypto-Fix-compiler-warning

totemcrypto: Fix compiler warning

Signed-off-by: Jan Friesse <jfriesse>
Comment 9 errata-xmlrpc 2017-09-05 11:24:10 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, 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-2017:2570
Note You need to log in before you can comment on or make changes to this bug.