summaryrefslogtreecommitdiff
path: root/src/node_report.cc
diff options
context:
space:
mode:
authorDaniel Bevenius <daniel.bevenius@gmail.com>2019-01-15 05:14:30 +0100
committerDaniel Bevenius <daniel.bevenius@gmail.com>2019-01-18 12:06:31 +0100
commitc0acece7ed70b3584474d646fcb8ef93204540b6 (patch)
tree1965b3010fd2217213e17c4fb3e2b3a72fc0642c /src/node_report.cc
parent2c0a75118cd6a2eaf6b45fe8c67336f44c86ab0f (diff)
downloadandroid-node-v8-c0acece7ed70b3584474d646fcb8ef93204540b6.tar.gz
android-node-v8-c0acece7ed70b3584474d646fcb8ef93204540b6.tar.bz2
android-node-v8-c0acece7ed70b3584474d646fcb8ef93204540b6.zip
test: use fipsMode instead of common.hasFipsCrypto
Currently, test-cli-node-print-help uses common.hasFipsCrypto to determine if the test should check for the existence of FIPS related options (--enable-fips, and --force-fips). The FIPS options are available when node has been compiled against an OpenSSL library with FIPS support in which case the test would verify that these options are available. But by using crypto.fips (which uses crypto.getFips()) this would only be checked when fips has been enabled, but these options are available regardless if FIPS is enabled or disabled. This commit updates the test to use fipsMode from config to determine if the FIPS options existence should be checked. PR-URL: https://github.com/nodejs/node/pull/25510 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Diffstat (limited to 'src/node_report.cc')
0 files changed, 0 insertions, 0 deletions