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

Open ssl 3 and node repo server #44649

Closed
sirdawidd opened this issue Sep 15, 2022 · 1 comment
Closed

Open ssl 3 and node repo server #44649

sirdawidd opened this issue Sep 15, 2022 · 1 comment
Labels
wrong repo Issues that should be opened in another repository.

Comments

@sirdawidd
Copy link

sirdawidd commented Sep 15, 2022

Version

17

Platform

docker node:18_alpine

Subsystem

No response

What steps will reproduce the bug?

Issue which I have is rather related to nodejs repository, as when I'm using nodejs with openssl3 to download any dependencies, nodejs server seems not support openssl3 so nodejs try to use "unsafe legacy renegotiation" which in my case is not possible as it's disabled via firewall (in my case https://www.paloaltonetworks.com) So seems that repository server is no RFC 5746 compliant.
I also created custom nodejs repository server on azure and there I dont facing any issues.

To reproduce run following dockerfile

FROM node:18-alpine 
RUN npm install -g  moment-timezone   

How often does it reproduce? Is there a required condition?

No response

What is the expected behavior?

https://registry.npmjs.org should be RFC 5746 compliant

What do you see instead?

9 70.85 npm verb stack FetchError: request to https://registry.npmjs.org/npm failed, reason: write EPROTO 88499062057F0000:error:0A000152:SSL routines:final_renegotiate:unsafe legacy renegotiation disabled:../deps/openssl/openssl/ssl/statem/extensions.c:907:
#9 70.85 npm verb stack
#9 70.85 npm verb stack     at ClientRequest.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:130:14)
#9 70.85 npm verb stack     at ClientRequest.emit (node:events:527:28)
#9 70.85 npm verb stack     at TLSSocket.socketErrorListener (node:_http_client:454:9)
#9 70.85 npm verb stack     at TLSSocket.emit (node:events:539:35)
#9 70.85 npm verb stack     at emitErrorNT (node:internal/streams/destroy:151:8)
#9 70.85 npm verb stack     at emitErrorCloseNT (node:internal/streams/destroy:116:3)
#9 70.85 npm verb stack     at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
#9 70.85 npm verb cwd /app
#9 70.85 npm verb Linux 5.10.76-linuxkit
#9 70.85 npm verb node v18.2.0
#9 70.85 npm verb npm  v8.9.0
#9 70.85 npm ERR! code EPROTO
#9 70.85 npm ERR! syscall write
#9 70.85 npm ERR! errno EPROTO
#9 70.85 npm ERR! request to https://registry.npmjs.org/npm failed, reason: write EPROTO 88499062057F0000:error:0A000152:SSL routines:final_renegotiate:unsafe legacy renegotiation disabled:../deps/openssl/openssl/ssl/statem/extensions.c:9

Additional information

No response

@bnoordhuis
Copy link
Member

The npm registry isn't maintained by the Node.js project. I'm not sure who does now that NPM is part of GitHub but maybe start here: https://github.com/npm

@bnoordhuis bnoordhuis closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2022
@bnoordhuis bnoordhuis added the wrong repo Issues that should be opened in another repository. label Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wrong repo Issues that should be opened in another repository.
Projects
None yet
Development

No branches or pull requests

2 participants