Skip to content
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

Allow unsafe legacy renegotiation on HTTPS #287

Merged

Conversation

caalberts
Copy link
Contributor

@caalberts caalberts commented Dec 11, 2022

Node.js 18 supports OpenSSL 3.0 which requires secure renegotiation by default. Since the units use self-signed cert without publicly available CA, the requests sent to the units need to be sent using HTTPS Agent with SSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION.

Fixes #279
Fixes #277.

Node.js 18 supports OpenSSL 3.0 which requires secure renegotiation by default.
Since the units use self-signed cert without publicly available CA,
the requests sent to the units need to be sent using
HTTPS Agent with SSL_OP_ALLOW_UNSAFE_LEGACY_RENEGOTIATION.
@caalberts
Copy link
Contributor Author

@cbrandlehner could you please take a look at this PR?

@cbrandlehner cbrandlehner self-requested a review December 11, 2022 19:42
@cbrandlehner cbrandlehner self-assigned this Dec 11, 2022
// the units use a self-signed cert and the CA doesn't seem to be publicly available.
// Node.js 18 supports OpenSSL 3.0 which requires secure renegotiation by default.
const unsafeAgent = new https.Agent({
rejectUnauthorized: false,

Check failure

Code scanning / CodeQL

Disabling certificate validation

Disabling certificate validation is strongly discouraged.
@cbrandlehner cbrandlehner merged commit dd16419 into cbrandlehner:master Dec 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants