Ania

Hi guys, I’ve heard from Kasperky Technical Support again and they informed me that the issue should be solved now. I switched back on the "check secure connection (https).." option in the preferences and checked all the websites - and they’re working now! ☺ Seems that the issue is solved! Hooray! Would advise you checking if it works for you too.

This is the reply I just received from the Kaspersky Technical Support. Same advice as mentioned already in this thread: “Recently an issue arose on Kaspersky Internet Security/Kaspersky Security Cloud on Mac, and you are unable to visit certain secure websites. We are aware of the issue, and our developers are working for a fix. At the moment, there is a workaround you can use to visit such websites. Please click on the Kaspersky icon on the top right corner and choose preferences. On the protection tab, disable the option "check secure connection (https).." and try to visit the website again. I suggest using this workaround to visit the secure websites but not the banking websites since Safe Money won't work after this workaround. If it's urgent to use your banking websites, please use another computer, preferably a Windows one. I will keep the incident open in our database and I will keep you posted by sending you a new email when we fix this issue permanently.” I will post an update here, once they let me know they have sorted out this issue. For now it just looks we have to keep operating without the Safe Money option. Hopefully it will happen sooner rather than later.

I also have the same problem. Receiving the following message when trying to access a number of websites: Your connection is not private Attackers might be trying to steal your information from ‘name of the website’ (for example, passwords, messages or credit cards). Learn more NET::ERR_CERT_VALIDITY_TOO_LONG The websites open fine once I uncheck the option next to "Check secure connections (HTTPS) for Safe Money and Private Browsing". Would be great to be updated on the situation and the progress of resolving this current bug. I also made a request with the Technical Support as advised by FLOOD.