4 ms·

As per Joe Grund: http://blog.npmjs.org/post/78085451721/npms-self-signed-certificate-is-no-more#comment-1264542895 http://blog.npmjs.org/post/78085451721/npms-

by ibash 13y ago

As per Joe Grund: http://blog.npmjs.org/post/78085451721/npms-self-signed-certificate-is-no-more#comment-1264542895 http://blog.npmjs.org/post/78085451721/npms-self-signed-cert... npm config set strict-ssl false npm update npm -g npm config set strict-ssl true

honksillet 13y ago
I was just about to post this link. The change broke bower at on my laptop. The above link fixed it.
awj 13y ago
That's ... still a dangerous way to accomplish the update. You're disabling a key safeguard that ensures you're actually talking to official npm servers, then re-enabling the safeguard after running the code that whoever-you-got-it-from provided. I'm sure the likelihood of experiencing a MITM attack here is low, but the security consideration needs to be as widely advertised as the solution.