Skip to content

Commit a965dda

Browse files
TrottMylesBorins
authored andcommitted
doc: simplify and clarify FIPS text in BUILDING.md
PR-URL: #17538 Fixes: #17536 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Jon Moss <[email protected]>
1 parent 24dc57b commit a965dda

File tree

1 file changed

+6
-10
lines changed

1 file changed

+6
-10
lines changed

BUILDING.md

+6-10
Original file line numberDiff line numberDiff line change
@@ -347,17 +347,13 @@ as `deps/icu` (You'll have: `deps/icu/source/...`)
347347

348348
## Building Node.js with FIPS-compliant OpenSSL
349349

350-
NOTE: Windows is not yet supported
350+
It is possible to build Node.js with the
351+
[OpenSSL FIPS module](https://www.openssl.org/docs/fipsnotes.html) on POSIX
352+
systems. Windows is not supported.
351353

352-
It is possible to build Node.js with
353-
[OpenSSL FIPS module](https://www.openssl.org/docs/fipsnotes.html).
354-
355-
**Note**: building in this way does **not** allow you to claim that the
356-
runtime is FIPS 140-2 validated. Instead you can indicate that the runtime
357-
uses a validated module. See the
358-
[security policy](http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1747.pdf)
359-
page 60 for more details. In addition, the validation for the underlying module
360-
is only valid if it is deployed in accordance with its
354+
Building in this way does not mean the runtime is FIPS 140-2 validated, but
355+
rather that the runtime uses a validated module. In addition, the validation for
356+
the underlying module is only valid if it is deployed in accordance with its
361357
[security policy](http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1747.pdf).
362358
If you need FIPS validated cryptography it is recommended that you read both
363359
the [security policy](http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1747.pdf)

0 commit comments

Comments
 (0)