Replies: 4 comments 2 replies
-
I've converted this to a discussion because the error message already hints at what's going on, and that isn't a node bug. |
Beta Was this translation helpful? Give feedback.
-
So, how to compile |
Beta Was this translation helpful? Give feedback.
-
Still no answer how to do it. |
Beta Was this translation helpful? Give feedback.
-
I'm too late, but I'll share what solved the problem for me. I faced this issue few days ago and fixed it by updating my
It seems that node was not using the correct |
Beta Was this translation helpful? Give feedback.
-
Version
v20.0.0-pre
Platform
Linux server 5.15.0-67-generic #74-Ubuntu SMP Wed Feb 22 14:14:39 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
Follow the instruction https://github.com/nodejs/node/blob/main/BUILDING.md#building-nodejs-with-fips-compliant-openssl to build
node
with quic support, but then I finnaly compile and testnode
:./node --enable-fips -p 'crypto.getFips()
, I got error:How often does it reproduce? Is there a required condition?
100%
What is the expected behavior? Why is that the expected behavior?
./node --enable-fips -p 'crypto.getFips()
must return1
as indicated in docs: https://github.com/nodejs/node/blob/main/BUILDING.md#building-nodejs-with-fips-compliant-opensslWhat do you see instead?
./node --enable-fips -p 'crypto.getFips()'
Additional information
ldd ./node
./node -p process.versions.openssl
./node -p 'process.config.variables.openssl_is_fips'
Beta Was this translation helpful? Give feedback.
All reactions