First, we should indeed patch the /etc openssl config to comment out the problematic section, especially since they are the same as the default.
Furthermore, we should also patch nodejs in Jammy *not to* look into this configuration file, as it'd be surprising for the user to have their nodejs programs fail with obscure errors when touching an unrelated config file, especially in ways that are presumably perfectly fine.
There are a couple of issues here.
First, we should indeed patch the /etc openssl config to comment out the problematic section, especially since they are the same as the default.
Furthermore, we should also patch nodejs in Jammy *not to* look into this configuration file, as it'd be surprising for the user to have their nodejs programs fail with obscure errors when touching an unrelated config file, especially in ways that are presumably perfectly fine.