-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FIPS and shared openssl #3077
Comments
+1 here — we openSUSE Tumbleweed users ran into this issue as well, see https://bugzilla.opensuse.org/show_bug.cgi?id=947747 |
@Nibbler999 there's hack that works this around should you need it — https://build.opensuse.org/package/view_file/home:msmeissn:branches:devel:languages:nodejs/nodejs/nodejs-no-fips.patch?rev=2 |
/cc @indutny :) |
Do not rely on `OPENSSL_FIPS` in `node_crypto.cc` when building with shared FIPS-enabled OpenSSL library. Enable FIPS in core only when configured with `--openssl-fips`. Fix: nodejs#3077
Should be fixed by #3153. Thanks! |
Fixed in 9bd26e7 |
Fix confirmed, thanks! |
Do not rely on `OPENSSL_FIPS` in `node_crypto.cc` when building with shared FIPS-enabled OpenSSL library. Enable FIPS in core only when configured with `--openssl-fips`. Fix: #3077 PR-URL: #3153 Reviewed-By: Ben Noordhuis <[email protected]>
So, is there a way to have FIPS and shared openssl? |
@kasicka Does |
Built on system without fips enabled:
Built on system with enabled fips has the same results, multiple tests failed.
I did not build it with --openssl-fips, because the fips functionality should be provided by openssl and I wasn't sure what to supply to the option. |
If you build against the system openssl in Fedora 23 (1.0.2d-fips) node tries to enable FIPS. This causes around 100 test failures/crashes. It would be better if it only enabled FIPS if you explicitly use --openssl-fips
The text was updated successfully, but these errors were encountered: