Bug 993441 - NSS needs to conform to new FIPS standard. [rhel-6.6]
NSS needs to conform to new FIPS standard. [rhel-6.6]
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: nss-softokn (Show other bugs)
6.5
Unspecified Unspecified
high Severity high
: rc
: 6.6
Assigned To: Elio Maldonado Batiz
Hubert Kario
:
Depends On:
Blocks: 1070830 RHEL6.6FIPS140
  Show dependency treegraph
 
Reported: 2013-08-05 20:04 EDT by Bob Relyea
Modified: 2014-10-14 01:02 EDT (History)
12 users (show)

See Also:
Fixed In Version: nss-softokn-3.14.3-13.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 993443 1004102 (view as bug list)
Environment:
Last Closed: 2014-10-14 01:02:40 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bob Relyea 2013-08-05 20:04:07 EDT
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:
Comment 1 Bob Relyea 2013-08-05 20:06:56 EDT
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.
Comment 5 Paul Wouters 2013-09-04 09:29:22 EDT
(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?
Comment 6 Eric Paris 2013-09-04 10:32:58 EDT
This bug must also be used to make sure that a -fips subpackage is created.  not just the self test fix.
Comment 7 Bob Relyea 2013-09-04 13:59:44 EDT
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).
Comment 12 Tomas Mraz 2013-12-04 10:38:33 EST
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
Comment 13 Bob Relyea 2014-03-24 19:17:41 EDT
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.
Comment 14 Tomas Mraz 2014-03-25 04:35:22 EDT
This is in conformance with FIPS requirements.
Comment 17 Bob Relyea 2014-04-22 17:11:38 EDT
fixed in nss-softokn-3.14.3-13.el6
Comment 22 errata-xmlrpc 2014-10-14 01:02:40 EDT
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

Note You need to log in before you can comment on or make changes to this bug.