You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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
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
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?
Additional information
No response
The text was updated successfully, but these errors were encountered: