-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
[Nodejs] --force-fips -p 'crypto.getFips()' - segfault patches
-
5% To Do, 11% In Progress, 84% Done
-
rhel-pt-ruby-nodejs
-
False
-
-
Unspecified
-
Unspecified
-
Unspecified
Description of issue:
As described in RHEL-104574 there is currently an issue with usage of
--force-fips -p 'crypto.getFips()'
resulting in segfault if patch is not included.
# node --force-fips -p 'crypto.getFips()' # node[7081]: std::shared_ptr<node::InitializationResultImpl> node::InitializeOncePerProcessInternal(const std::vector<std::__cxx11::ba sic_string<char> >&, ProcessInitializationFlags::Flags) at ../../src/node.cc:1236 # Assertion failed: ncrypto::CSPRNG(nullptr, 0) ----- Native stack trace ----- 1: 0x7f9eee5a5a87 node::Assert(node::AssertionInfo const&) [/lib64/libnode.so.127] 2: 0x7f9eee56e6f8 [/lib64/libnode.so.127] 3: 0x7f9eee56fc7c node::Start(int, char**) [/lib64/libnode.so.127] 4: 0x7f9eed85130e [/lib64/libc.so.6] 5: 0x7f9eed8513c9 __libc_start_main [/lib64/libc.so.6] 6: 0x555712b40035 _start [node] Aborted (core dumped)
This patch has been last added to nodejs18 and is missing from nodejs20/22/24.
Definition of done:
Since resolving the issue upstream might take considerable time, it should be desirable to prevent the segfault in the meantime by including the patch.
- is incorporated by
-
-
- New
-