-
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
FreeBSD openssl version string doesn't match regex test #43078
Comments
Did you compile Node.js yourself? If so, what flags did you pass to |
This would have been from FreeBSD poudriere using the ports tree updated for 14.9.2 WIP. This would have used the base system openssl due to args:
ENV:
|
@nodejs/testing @nodejs/crypto I don't think adding the string "freebsd" is the way to go, but maybe changing the allowance for "fips" to be a general allowance of alpha or alphanumeric strings? We might also add some logic to detect built-in vs. system OpenSSL? Maybe skip the check entirely if OpenSSL is the system one, or at least make it much more lax? |
I think when built with a shared openssl allowing pretty much anything for |
Relax the OpenSSL version check when Node.js is built with the `--shared-openssl` option. Verify only that `process.versions.openssl` is truthy. Fixes: nodejs#43078
Relax the OpenSSL version check when Node.js is built with the `--shared-openssl` option. Verify only that `process.versions.openssl` is truthy. Fixes: nodejs/node#43078 PR-URL: nodejs/node#50505 Reviewed-By: Richard Lau <rlau@redhat.com>
Relax the OpenSSL version check when Node.js is built with the `--shared-openssl` option. Verify only that `process.versions.openssl` is truthy. Fixes: nodejs/node#43078 PR-URL: nodejs/node#50505 Reviewed-By: Richard Lau <rlau@redhat.com>
Test
test-process-versions
Platform
FreeBSD
Console output
Build links
No response
Additional information
node output of
process.versions.openssl
It seems the regex could change to:
/^\d+\.\d+\.\d+[a-z]?(-freebsd|-fips)?$
Adding the
-freebsd
The text was updated successfully, but these errors were encountered: