Tjyylli

I can't die. Who am I?

Recommendation letter by significant other if you worked with them professionally?

The meaning of ‘otherwise’

Does "Until when" sound natural for native speakers?

In the late 1940’s to early 1950’s what technology was available that could melt ice?

What do you call someone who likes to pick fights?

ER diagram relationship node size adjustment

Expressing logarithmic equations without logs

How do spaceships determine each other's mass in space?

Can I negotiate a patent idea for a raise, under French law?

Does Christianity allow for believing on someone else's behalf?

Rationale to prefer local variables over instance variables?

What will be the sign of work done?

Making a kiddush for a girl that has hard time finding shidduch

Called into a meeting and told we are being made redundant (laid off) and "not to share outside". Can I tell my partner?

Dynamic Linkage of LocatorPane and InputField

Do I really need to have a scientific explanation for my premise?

Power Strip for Europe

Is it safe to abruptly remove Arduino power?

Readonly vs static readonly clarification

Doubts in understanding some concepts of potential energy

Can we track matter through time by looking at different depths in space?

Help understanding 1986 schematic for Rohde & Schwarz cryptographic key generator

What sort of fish is this

Self signed Certificate Warning for Chrome browser

WS2003 + IIS = Untrusted CertificateChrome still shows red cross “https://” even with valid certificateCreating stronger self signed certificate(Chrome on) Windows 8 complains certificate not yet validhow can i found the source of a malware that is trying to force-open a websiteSelf-signed certificate becomes invalid after some timeMongoDB: Getting SSL peer certificate validation failed: self signed certificateSelf-signed certificate for IISHow to fix Firefox 59 no longer accepting my self signed SSL certificate on .dev virtualhostChrome: NET::ERR_CERT_DATE_INVALID for self signed certificate?

0

After booting, on the first launch of Chrome browser, every time I see a pair of self signed root certificate warnings by Kaspersky Antivirus. It happens only with Chrome, and not with Firefox or IE.

I been seeing this for past few days, and when I view certificate, it's a 4 set, alphanumerical string separated by dashes total of 32 characters. The certificate always has 2 days validity, and everyday it updates validity. For instance today it's 2/18-2/20, yesterday it was 2/17-2/19

25a029c5-c3f7-32b8-2caa-1667e6fa9b13

Kaspersky Warning about first Certificate

Certificate Properites

Kaspersky Warning about second Certificate

I initially thought it's related to an add-on, but been seeing this even after disabling extensions on Chrome. The properties did not reveal much about the certificate itself, the "issued to" and "issued by" are same.

I am curious about this, and hoping if someone can tell me about this certificate. I'm suspicious that my Chrome is infected by Adware/Spyware. I'm going to try and reinstall Chrome to see if problem persists.

Update 1: I tried reinstall, delete Chrome folder completely, but not one them got rid of Certificate warning. Not sure but this may not be related/limited to Chrome.

google-chrome ssl ssl-certificate

share|improve this question

edited Feb 19 at 2:34

bobby789

asked Feb 19 at 1:47

bobby789bobby789

11

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Are the certificates installed in the certificate store?
  
  – Ramhound
  Feb 19 at 2:03
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  No I couldn't find these two in the store.
  
  – bobby789
  Feb 19 at 2:32
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  You don’t specify any information in the website your attempting to visit. Legitimate Root certificates are valid for more than 2 days.
  
  – Ramhound
  Feb 19 at 2:44
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @bobby789 Anecdotally, at one point I had a piece of software (a video streaming server) that was operating locally on port 80 handing out invalid certificates for a web site hosted on the same server. Not saying this has anything directly to do with what you are experiencing, but you may wish to investigate any programs running on your PC that might be serving these.
  
  – Anaksunaman
  Feb 19 at 3:49
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Ramhound The certificate warning appears as soon as I open the browser. I did a wireshark capture, but found nothing suspicious in the external IP address that my system communicated with. I'm going to re-do the Wireshark capture to identify if the system/chrome is reaching out to a specific IP/domain, when the certificate warning appears. However it's very possible that Kapersky warning is not real-time.
  
  – bobby789
  Feb 19 at 11:06
  

  
  
  
  

 | 
show 8 more comments

0

After booting, on the first launch of Chrome browser, every time I see a pair of self signed root certificate warnings by Kaspersky Antivirus. It happens only with Chrome, and not with Firefox or IE.

I been seeing this for past few days, and when I view certificate, it's a 4 set, alphanumerical string separated by dashes total of 32 characters. The certificate always has 2 days validity, and everyday it updates validity. For instance today it's 2/18-2/20, yesterday it was 2/17-2/19

25a029c5-c3f7-32b8-2caa-1667e6fa9b13

Kaspersky Warning about first Certificate

Certificate Properites

Kaspersky Warning about second Certificate

I initially thought it's related to an add-on, but been seeing this even after disabling extensions on Chrome. The properties did not reveal much about the certificate itself, the "issued to" and "issued by" are same.

I am curious about this, and hoping if someone can tell me about this certificate. I'm suspicious that my Chrome is infected by Adware/Spyware. I'm going to try and reinstall Chrome to see if problem persists.

Update 1: I tried reinstall, delete Chrome folder completely, but not one them got rid of Certificate warning. Not sure but this may not be related/limited to Chrome.

google-chrome ssl ssl-certificate

share|improve this question

edited Feb 19 at 2:34

bobby789

asked Feb 19 at 1:47

bobby789bobby789

11

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Are the certificates installed in the certificate store?
  
  – Ramhound
  Feb 19 at 2:03
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  No I couldn't find these two in the store.
  
  – bobby789
  Feb 19 at 2:32
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  You don’t specify any information in the website your attempting to visit. Legitimate Root certificates are valid for more than 2 days.
  
  – Ramhound
  Feb 19 at 2:44
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @bobby789 Anecdotally, at one point I had a piece of software (a video streaming server) that was operating locally on port 80 handing out invalid certificates for a web site hosted on the same server. Not saying this has anything directly to do with what you are experiencing, but you may wish to investigate any programs running on your PC that might be serving these.
  
  – Anaksunaman
  Feb 19 at 3:49
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @Ramhound The certificate warning appears as soon as I open the browser. I did a wireshark capture, but found nothing suspicious in the external IP address that my system communicated with. I'm going to re-do the Wireshark capture to identify if the system/chrome is reaching out to a specific IP/domain, when the certificate warning appears. However it's very possible that Kapersky warning is not real-time.
  
  – bobby789
  Feb 19 at 11:06
  

  
  
  
  

 | 
show 8 more comments

After booting, on the first launch of Chrome browser, every time I see a pair of self signed root certificate warnings by Kaspersky Antivirus. It happens only with Chrome, and not with Firefox or IE.

I been seeing this for past few days, and when I view certificate, it's a 4 set, alphanumerical string separated by dashes total of 32 characters. The certificate always has 2 days validity, and everyday it updates validity. For instance today it's 2/18-2/20, yesterday it was 2/17-2/19

25a029c5-c3f7-32b8-2caa-1667e6fa9b13

Kaspersky Warning about first Certificate

Certificate Properites

Kaspersky Warning about second Certificate

I initially thought it's related to an add-on, but been seeing this even after disabling extensions on Chrome. The properties did not reveal much about the certificate itself, the "issued to" and "issued by" are same.

I am curious about this, and hoping if someone can tell me about this certificate. I'm suspicious that my Chrome is infected by Adware/Spyware. I'm going to try and reinstall Chrome to see if problem persists.

Update 1: I tried reinstall, delete Chrome folder completely, but not one them got rid of Certificate warning. Not sure but this may not be related/limited to Chrome.

google-chrome ssl ssl-certificate

share|improve this question

edited Feb 19 at 2:34

bobby789

asked Feb 19 at 1:47

bobby789bobby789

11

share|improve this question

edited Feb 19 at 2:34

bobby789

asked Feb 19 at 1:47

bobby789bobby789

11

share|improve this question

edited Feb 19 at 2:34

bobby789

asked Feb 19 at 1:47

bobby789bobby789

11

asked Feb 19 at 1:47

bobby789bobby789

11

asked Feb 19 at 1:47

bobby789bobby789

11

1 Answer
1

active

oldest

votes

0

I contacted Kaspersky, who confirmed that this is a known issue caused by devices like Chromecast on the network.

They offered a temporary fix, however before I could implement the fix, I stopped seeing the certificate warning, so I'm guessing Kaspersky fixed it.

For anyone interested in knowing the Kaspersky's workaround, here it is

#

If using Chromecast or other Google Devices, please follow this guide:

1. Reproduce the issue and keep our product notification open. (required for step 4)


2. Open main Kaspersky window - More tools - My network - Network monitor;


3. Sort the table by Port (or type in Chrome in the search field);


4. Find the port 8009 used by Google Chrome ​and note down the IP address used by it (like 192.168.0.x).


5. Afterwards open Kaspersky settings (gear icon at the bottom left) - protection - application control - manage applications;


6. In the search field type "chrome";


7. Double click the Google Chrome application and go to "Exclusions"


8. Tick the "Do not scan all traffic" and select "Do not scan encrypted traffic";


9. Tick on "Only for specified IP addresses" - enter the IP address from step 4.


10. Tick on "Only for specified ports" - 8009


11. Click Save.

share

answered 3 mins ago

bobby789bobby789

11

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1407256%2fself-signed-certificate-warning-for-chrome-browser%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

I contacted Kaspersky, who confirmed that this is a known issue caused by devices like Chromecast on the network.

They offered a temporary fix, however before I could implement the fix, I stopped seeing the certificate warning, so I'm guessing Kaspersky fixed it.

For anyone interested in knowing the Kaspersky's workaround, here it is

#

If using Chromecast or other Google Devices, please follow this guide:

1. Reproduce the issue and keep our product notification open. (required for step 4)


2. Open main Kaspersky window - More tools - My network - Network monitor;


3. Sort the table by Port (or type in Chrome in the search field);


4. Find the port 8009 used by Google Chrome ​and note down the IP address used by it (like 192.168.0.x).


5. Afterwards open Kaspersky settings (gear icon at the bottom left) - protection - application control - manage applications;


6. In the search field type "chrome";


7. Double click the Google Chrome application and go to "Exclusions"


8. Tick the "Do not scan all traffic" and select "Do not scan encrypted traffic";


9. Tick on "Only for specified IP addresses" - enter the IP address from step 4.


10. Tick on "Only for specified ports" - 8009


11. Click Save.

share

answered 3 mins ago

bobby789bobby789

11

add a comment | 

0

I contacted Kaspersky, who confirmed that this is a known issue caused by devices like Chromecast on the network.

They offered a temporary fix, however before I could implement the fix, I stopped seeing the certificate warning, so I'm guessing Kaspersky fixed it.

For anyone interested in knowing the Kaspersky's workaround, here it is

#

If using Chromecast or other Google Devices, please follow this guide:

1. Reproduce the issue and keep our product notification open. (required for step 4)


2. Open main Kaspersky window - More tools - My network - Network monitor;


3. Sort the table by Port (or type in Chrome in the search field);


4. Find the port 8009 used by Google Chrome ​and note down the IP address used by it (like 192.168.0.x).


5. Afterwards open Kaspersky settings (gear icon at the bottom left) - protection - application control - manage applications;


6. In the search field type "chrome";


7. Double click the Google Chrome application and go to "Exclusions"


8. Tick the "Do not scan all traffic" and select "Do not scan encrypted traffic";


9. Tick on "Only for specified IP addresses" - enter the IP address from step 4.


10. Tick on "Only for specified ports" - 8009


11. Click Save.

share

answered 3 mins ago

bobby789bobby789

11

add a comment | 

I contacted Kaspersky, who confirmed that this is a known issue caused by devices like Chromecast on the network.

They offered a temporary fix, however before I could implement the fix, I stopped seeing the certificate warning, so I'm guessing Kaspersky fixed it.

For anyone interested in knowing the Kaspersky's workaround, here it is

#

If using Chromecast or other Google Devices, please follow this guide:

1. Reproduce the issue and keep our product notification open. (required for step 4)


2. Open main Kaspersky window - More tools - My network - Network monitor;


3. Sort the table by Port (or type in Chrome in the search field);


4. Find the port 8009 used by Google Chrome ​and note down the IP address used by it (like 192.168.0.x).


5. Afterwards open Kaspersky settings (gear icon at the bottom left) - protection - application control - manage applications;


6. In the search field type "chrome";


7. Double click the Google Chrome application and go to "Exclusions"


8. Tick the "Do not scan all traffic" and select "Do not scan encrypted traffic";


9. Tick on "Only for specified IP addresses" - enter the IP address from step 4.


10. Tick on "Only for specified ports" - 8009


11. Click Save.

share

answered 3 mins ago

bobby789bobby789

11

share

answered 3 mins ago

bobby789bobby789

11

answered 3 mins ago

bobby789bobby789

11

answered 3 mins ago

bobby789bobby789

11