Replies: 0 comments 7 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. |
|
So, how to compile |
|
Still no answer how to do it. |
|
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 |
|
Your issue appears to be related to OpenSSL’s FIPS module configuration, not Node.js itself. The error: OpenSSL error when trying to enable FIPS: If
Conclusion:The issue is not a bug in Node.js, but rather a misconfigured OpenSSL setup. Updating Let me know if you need further clarification! |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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
nodewith 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 return1as 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'All reactions