Skip to content

Commit 8e4cb1b

Browse files
Trottgibfahn
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 fb33231 commit 8e4cb1b

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
@@ -351,17 +351,13 @@ as `deps/icu` (You'll have: `deps/icu/source/...`)
351351

352352
## Building Node.js with FIPS-compliant OpenSSL
353353

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

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

0 commit comments

Comments
 (0)