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:

In NSS the value of the PKCS#11 constants were swapped.

Version-Release number of selected component (if applicable):

nss-3.44-14

How reproducible:

Very

Steps to Reproduce:
1. Install NSS
2. Check the value of /usr/include/nss3/pkcs11t.h
3. Compare the values of CKM_AES_CMAC against PKCS#11 spec (v2.40 or greater). 

Actual results:

CKM_AES_CMAC has the value of CKM_AES_CMAC_GENERAL and visa-versa.

Expected results:

They should match what's in the spec.

Additional info:

This limits iter-op with HSMs, should be fixed for release.

Setting blocker? per discussion with Bob.

1. If the bug is not resolved, we will be incompatible with PKCS #11 modules that use the correct numbers. This means customers with HSMs will fail.
2. Low risk: anything that worked before the change will continue to work after the change.
3. This is a low risk, high reward patch.

Fixed in nss-3.44.0-15.el8

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-2020:1638