-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
[Node.js] - core dump with --force/enable-fips
-
100% To Do, 0% In Progress, 0% Done
-
rhel-pt-ruby-nodejs
-
False
-
-
Unspecified
-
Unspecified
-
Unspecified
Description of problem:
There is coredump occurring during force-fips or -enable-fips. Issue was previosly tracked on RHELPLAN-163528 and then in this github issue.
This seems to be connected to loading of default openssl fips providers on systems which use openssl version >= v3 as tests on RHEL v8.10 with openssl v1.1 do not result in core dumb.
Steps to Reproduce:
1.run node --force-fips -p 'crypto.getFips()' or node --enable-fips
2.
3.
Result:
# node[2255]: std::shared_ptr<node::InitializationResultImpl> node::InitializeOncePerProcessInternal(const std::vector<std::__cxx11::basic_string<char> >&, ProcessInitializationFlags::Flags) at ../../src/node.cc:1235 # Assertion failed: ncrypto::CSPRNG(nullptr, 0) ----- Native stack trace ----- 1: 0x7f062b414257 node::Assert(node::AssertionInfo const&) [/lib64/libnode.so.127] 2: 0x7f062b3da8a8 [/lib64/libnode.so.127] 3: 0x7f062b3dbc5c node::Start(int, char**) [/lib64/libnode.so.127] 4: 0x7f062b0125b5 [/lib64/libc.so.6] 5: 0x7f062b012668 __libc_start_main [/lib64/libc.so.6] 6: 0x563722e40035 _start [node]
- incorporates
-
-
- In Progress
-
-
RHEL-105956 [Node.js] [Investigation] - Investigate current state of --force/enable-fips flags
-
- New
-
