Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
libreswan's compiled against nss from a few weeks ago works finr. But if nss is upgraded, due to a change in nss, the libreswan aes_gcm code fails. Luckily libreswan does a selftest on boot, so this is obvious and libreswan fails to start using:
jambuf = {array = 0x7ffc4f3c8d20 "ABORT: ASSERTION FAILED: test_gcm_vectors(&ike_alg_encrypt_aes_gcm_16, aes_gcm_tests) (in test_ike_alg() at ike_alg_test.c:41)", total = 126, roof = 1023,
The workaround for this is to recompile libreswan and setting:
#define NSS_PKCS11_2_0_COMPAT 1
When compiled with that, libreswan remains using the old nss abi properly
This problem has been spotted on various distributions, including fedora.
The failure scenario is upgrading nss on its own.
While this fix may come too late for some (if they dont pull in a new libreswan, and do pull in a new nss, the problem manifests itself), having a newer libreswan available would work around the problem as well. In addition, the newer libreswan is ensured to not use a different nss api then expected.
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 (libreswan 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/RHEA-2020:4722
libreswan's compiled against nss from a few weeks ago works finr. But if nss is upgraded, due to a change in nss, the libreswan aes_gcm code fails. Luckily libreswan does a selftest on boot, so this is obvious and libreswan fails to start using: jambuf = {array = 0x7ffc4f3c8d20 "ABORT: ASSERTION FAILED: test_gcm_vectors(&ike_alg_encrypt_aes_gcm_16, aes_gcm_tests) (in test_ike_alg() at ike_alg_test.c:41)", total = 126, roof = 1023, The workaround for this is to recompile libreswan and setting: #define NSS_PKCS11_2_0_COMPAT 1 When compiled with that, libreswan remains using the old nss abi properly This problem has been spotted on various distributions, including fedora. The failure scenario is upgrading nss on its own. While this fix may come too late for some (if they dont pull in a new libreswan, and do pull in a new nss, the problem manifests itself), having a newer libreswan available would work around the problem as well. In addition, the newer libreswan is ensured to not use a different nss api then expected.