News for hackers. Stuff that matters.
Re:Patch Critical Cryptographic Vulnerability in Microsoft W... by est31 on Tuesday January 14, 2020 @03:46PM (#22049075)
> connections to the npm package server

Doesn't npm use node.js for this, which uses openssl?

> https://nodejs.org/api/tls.html#tls_tls_ssl

Third party tools connecting to the npm server that use Window's TLS library would absolutely be affected though.

Re:Patch Critical Cryptographic Vulnerability in Microsoft W... by thw0rted on Wednesday January 15, 2020 @03:20AM (#22052550)
I suspect the answer is "it's complicated". For example, you can specify a package version string as `git://...` and it will grab the package from a git repository. It's possible that this uses a JS-native Git implementation, but it's also possible that it uses a locally-installed Git binary, which could in turn use MSCAPI, especially if it's configured to use an external SSH provider.
Re:Patch Critical Cryptographic Vulnerability in Microsoft W... by est31 on Wednesday January 15, 2020 @06:41PM (#22060101)
That's a good point. I'm not too familiar with npm code but it seems that they are indeed using git from the CLI instead using it via a library: https://github.com/npm/cli/blob/ba7f1466436cc22e27f8a14dede3...