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.
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Argg.... bugzilla took cr as an "ok let's create the bug... here.s the real description...
Description of problem:
( from the testing lab... )
just today and effective immediately there is a new IG published. This
new IG affects all user space libraries.
The self tests must be invoked by a .ctor entry: see
http://csrc.nist.gov/groups/STM/cmvp/documents/fips140-2/FIPS1402IG.pdf
page 116 (section 9.10).
It is from now on disallowed that the calling app invokes the init
function for executing the self tests. The self test functions must be
invoked with a void __attribute__((contructor)) function.
For the kernel module, the
self test must be invoked in the __init function -- I think that is the
case with the testmgr.
How reproducible:
Inspection.
(In reply to Bob Relyea from comment #1)
> It is from now on disallowed that the calling app invokes the init
> function for executing the self tests. The self test functions must be
> invoked with a void __attribute__((contructor)) function.
So openswan must now call the test function? If so, can you tell me what to call?
Paul, No. The test function will be called by the OS at DLL load time. Applications don't need to do anything (This basically moves the test function from NSS_Init time to load time).
Actually the -fips subpackage will not be created. The FIPS mode tests should be based on this table:
| /etc/system-fips | no /etc/system-fips
---------------------+------------------+----------------------
kernel fips flag | enforce | no test/no fips
---------------------+------------------+------
no kernel fips flag | test | no test
test = verify checksums only
enforce = verify checksums & abort in case of failure
To be clear, NSS implements the /etc/system-fips side of this equation, as NSS can be put in FIPS mode whether or not the system is in fips-mode
| |
-------------------+-------------+
NSS db in FIPS | enforce |
-------------------+-------------+
NSS db not in FIPS | test |
-------------------+-------------+
test = verify checksums (and POST) only
enforce = verify checksums (and POST) at load time, abort a init time if failed.
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.
http://rhn.redhat.com/errata/RHBA-2014-1378.html