unable to verify first certificate #193
Replies: 6 comments 6 replies
-
Sorry for not answering sooner. But what your describing are two very separate issues. The flag on virus total is not related to the certificate issue within PPM. If you'd like to read more about why there's a warning on virus total take a look here. But TLDR, a dependency of a dependency on installation prints a message in Russian, calling for peace. Because of current world events. For some reason this call for peace is being flagged as malicious behavior in some tools virus total uses. You can read more about what HOAX.JS.MSG actually means here. Which confirms that it's because of, in Kaspersky's own words "...undeclared functionality that displays certain messages, which is triggered depending on the time zone." But it is interesting that |
Beta Was this translation helpful? Give feedback.
-
I do not use NPM I was just reading around and trying everything I could. Thanks for explaining the Virus total false positive. I was starting to think the worst when I could not get it anything to work. So that’s the only hope in getting this to work is turning strict ssl off? Thanks for the reply and I apologize for thinking the worst.Sent from my iPhoneOn Jun 25, 2023, at 5:09 PM, confused_techie ***@***.***> wrote:
Sorry for not answering sooner. But what your describing are two very separate issues. The flag on virus total is not related to the certificate issue within PPM.
If you'd like to read more about why there's a warning on virus total take a look here. But TLDR, a dependency of a dependency on installation prints a message in Russian, calling for peace. Because of current world events. For some reason this call for peace is being flagged as malicious behavior in some tools virus total uses. You can read more about what HOAX.JS.MSG actually means here. Which confirms that it's because of, in Kaspersky's own words "...undeclared functionality that displays certain messages, which is triggered depending on the time zone."
So I assure you nothing within Pulsar itself is actually malicious, but I understand the warning is concerning.
But it is interesting that ppm config set strict-ssl false didn't work for you. Do you happen to use NPM at all? Is that working for you with any special configuration? Since ppm uses an older version of NPM internally so that may provide us an answer here
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Yes you are correct there is a root SSL certificate that is not being recognized and that’s why I tried the NPN command to see if I could reference the certificate as a trusted one. When I ran that command it appeared to run though when I tried to install I got errors again. I will retrace my steps and send you the output as soon as I get to my computer.Sent from my iPhoneOn Jun 25, 2023, at 7:27 PM, confused_techie ***@***.***> wrote:
No worries, I totally understand the concern about getting an alert from a virus scanner.
But that's all I'm aware of that could be done to resolve that issue. But I'm sure there's gotta be something else we can do to get it working.
Are you aware of why you are having SSL errors in the first place? Are you using some kind of VPN, or at a workplace that's providing it's own SSL certificates to decrypt traffic? PPM does support setting up a proxy, if that's something that could work for you?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Hello Here is the error I get and I did a fresh install and did the ppm config set strict-ssl false command from the terminal. I really appreciate you helping me out.(node:1201) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.(Use `node --trace-warnings ...` to show where the warning was created)npm ERR! cb() never called!npm ERR! This is an error with npm itself. Please report this error at:npm ERR! <https://npm.community>Sent from my iPhoneOn Jun 25, 2023, at 8:00 PM, ***@***.***> wrote:Yes you are correct there is a root SSL certificate that is not being recognized and that’s why I tried the NPN command to see if I could reference the certificate as a trusted one. When I ran that command it appeared to run though when I tried to install I got errors again. I will retrace my steps and send you the output as soon as I get to my computer.Sent from my iPhoneOn Jun 25, 2023, at 7:27 PM, confused_techie ***@***.***> wrote:
No worries, I totally understand the concern about getting an alert from a virus scanner.
But that's all I'm aware of that could be done to resolve that issue. But I'm sure there's gotta be something else we can do to get it working.
Are you aware of why you are having SSL errors in the first place? Are you using some kind of VPN, or at a workplace that's providing it's own SSL certificates to decrypt traffic? PPM does support setting up a proxy, if that's something that could work for you?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
The irony of all of this is it says to find more information about the error at https://npm.communityWhen I try to go there I get an SSL error in my browser as well. Sent from my iPhoneOn Jun 25, 2023, at 8:29 PM, ***@***.***> wrote:Hello Here is the error I get and I did a fresh install and did the ppm config set strict-ssl false command from the terminal. I really appreciate you helping me out.(node:1201) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.(Use `node --trace-warnings ...` to show where the warning was created)npm ERR! cb() never called!npm ERR! This is an error with npm itself. Please report this error at:npm ERR! <https://npm.community>Sent from my iPhoneOn Jun 25, 2023, at 8:00 PM, ***@***.***> wrote:Yes you are correct there is a root SSL certificate that is not being recognized and that’s why I tried the NPN command to see if I could reference the certificate as a trusted one. When I ran that command it appeared to run though when I tried to install I got errors again. I will retrace my steps and send you the output as soon as I get to my computer.Sent from my iPhoneOn Jun 25, 2023, at 7:27 PM, confused_techie ***@***.***> wrote:
No worries, I totally understand the concern about getting an alert from a virus scanner.
But that's all I'm aware of that could be done to resolve that issue. But I'm sure there's gotta be something else we can do to get it working.
Are you aware of why you are having SSL errors in the first place? Are you using some kind of VPN, or at a workplace that's providing it's own SSL certificates to decrypt traffic? PPM does support setting up a proxy, if that's something that could work for you?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Hello,
I get this error when I try to use the package manager. unable to verify first certificate. I checked online and I saw that some people had the same problem with atom though that solution did not work for me. I am using this with Mac OS. I have installed shell commands and I was able to run this ppm config set strict-ssl false I also ran this ppm config set NODE_TLS_REJECT_UNAUTHORIZED 0 and it did not help. I get the same error. is there a way to install a trusted root certificate? I think I figured it out. Just uploaded your Program to virus Total and its flagged as Hoax.JS.ExtMsg.a
Beta Was this translation helpful? Give feedback.
All reactions