kaspersky says licenses expired

Started by Formless, October 01, 2021, 09:13:07 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Formless

So all of a sudden kaspersky now requires me to give permission to access any website (including elliquiy) every 30 minutes.

I have no idea why it happened. Yesterday everything was working smoothly but today seems no matter what website I click on from my favorite or white listed domains, this pop up cones up:



The text isn’t clear and in arabic, but it says

Up top:
Cannot guarantee the domain you’re trying to connect to

App
Website

Error: one of the certificates in this string is not updated.

Thing is, it says that about any website so I know its a kaspersky problem rather than a website problem.

If anyone can help me figure this out, it’ll be greatly appreciated.

Vekseid

Does it happen with https://www.google.com or https://www.whitehouse.gov, or just most of the sites you've been visiting lately?

Your description makes it sound suspiciously like it's breaking on Let's Encrypt certs (which Elliquiy and most anyone but government, banking, or major sites use these days), which would point to its own solution somewhere.

If it's every site, or even if not, is it able to specify which 'certificate in the string' is not updated and could you post that certificate if so (for Elliquiy)? It might instead give you a fingerprint, I can use that also.

Formless

Quote from: Vekseid on October 01, 2021, 11:37:33 AM
Does it happen with https://www.google.com or https://www.whitehouse.gov, or just most of the sites you've been visiting lately?

Nope. Google & youtube are fine. Though I get some pop-ups while watching a video on youtube. I think these are related to ads? As for the Whitehouse, it opened up no problem.

Quote from: Vekseid on October 01, 2021, 11:37:33 AMIf it's every site, or even if not, is it able to specify which 'certificate in the string' is not updated and could you post that certificate if so (for Elliquiy)? It might instead give you a fingerprint, I can use that also.

Its pretty much any website I frequently visit. Even twitter and 500px.

As for the string of certificates, when I click on details here's what comes up:

DST root CA X3 this one appears at the top. And when I highlight it, it reads "This certificate has expired or no longer valid."

Below it:

R3. And when I highlight it, it reads "This certificate has expired or no longer valid."

Then below it comes the certificate for any given website. Which always reads that the certificate is valid.

So I guess, the problem is in the DTS and R3?

For the record, I can be rather clueless with these stuff and the stuff being in Arabic doesn't help.

Formless

A bit of an update.

It seems the DST root CA X3 has expired on September 30th.

I suppose downloading the new root from Let's encrypt will solve the problem?

If it helps, I'm using Win7

Vekseid

The site's been serving the new certificate for awhile now. For some reason your browser or something in your stack is insisting on using the older certificate bundle.

There should be a lock icon next to https://elliquiy.com in your browser's address bar, allowing you to view the certificate ('more information', a certificate-like button, etc). There are three parts:

Elliquiy.com's cert. This should be
Not Before/Issue Date: Tue, 28 Sep 2021 15:36:05 GMT
Not After/Expire Date: Mon, 27 Dec 2021 15:36:04 GMT

The middle part should be the R3 certificate (Let's Encrypt), and the base certificate is now the ISRG Root X1, which has replaced the DST root. You shouldn't need to download anything, unless you are still using Internet Explorer somehow and for some reason.

What browser(s) are you using?

Formless

I'm only using chrome.

And when I clicked on the lock icon, it does say the certificate is valid.

Still, every 30 minutes, the same permission to view the website pops up. Which is the really annoying issue here.

Formless

Well, I removed the DST root certificate and put the ISRG in its place and everything's back to normal.

Thanks.

Vekseid

Hrm. It should have happened automagically, even on Windows 7.

Glad things are working now though.