Updating Firefox to version 65

[jose.gimenez.47]

Apparently updating firefox to version 65 causes connection not secure everywhere. If I disable shield control there is no problem. I don´t know if is a problem with Firefox or Avast.
Thanks.

[Hopper15]

Apparently updating firefox to version 65 causes connection not secure everywhere. If I disable shield control there is no problem. I don´t know if is a problem with Firefox or Avast.
Thanks.

Same issue here. I'm pretty certain disabling https scanning would end it but I'm not going there.

[DavidR]

I think that we are going to be seeing more of this.

See https://forum.avast.com/index.php?topic=9671.msg1492179#msg1492179 which refers to:
Firefox 65 to show ‘Mozilla_PKIX_ERROR_ MITM_Detected’ when AV interferes with SSL connections

There is also a link for further information, I haven't installed FF 65 yet and will be waiting.

[Michael529]

Apparently updating firefox to version 65 causes connection not secure everywhere. If I disable shield control there is no problem. I don´t know if is a problem with Firefox or Avast.
Thanks.

No problem here with Firefox 65 (x64) and Avast Free 19.1.2360 running on Windows 10 (x64).

[alanb]

I think that we are going to be seeing more of this.

Just an observation (but may be pertinent).  The last time this flurry of reports happened was when Avast went to version 14: the problem was that the Avast certificate changed and a re-import of the certificate was the solution.

At that time the Avast cert was set to expire in 2024.  I just checked, and the current cert is set to expire in 2040, so it looks like it has changed again.

NOTE: in either case below, you must export the certificate from the latest Avast you are using.

So, as a first step, see if this helps https://support.avast.com/en-eu/article/Troubleshoot-invalid-email-certificate.

If not this may help (the reply was for Thunderbird, but applies equally for Firefox): https://forum.avast.com/index.php?topic=224844.msg1492272#msg1492272. 

[abruptum]

I did this :

  https://www.youtube.com/watch?v=lFMu0UVgM24

[alanb]

That would have been my next suggestion if https://forum.avast.com/index.php?topic=224844.msg1492272#msg1492272 doesn't work

[schmidthouse]

I personally am not seeing this issue with latest FF

[TheSharku]

I personally am not seeing this issue with latest FF

Same, although when I go to see site security, it now says it's verified by Avast. And it's like this in every site, it certainly was not like this before

[mchain]

I personally am not seeing this issue with latest FF

Same, although when I go to see site security, it now says it's verified by Avast. And it's like this in every site, it certainly was not like this before

Confirmed no issue.  Not aware that Avast ever stopped verification, but avast forum shows DigiCert, Inc as secure certificate

[TheSharku]

Confirmed no issue.  Not aware that Avast ever stopped verification, but avast forum shows DigiCert, Inc as secure certificate

It was probably an individual issue then, what got fixed yesterday when i reinstalled Firefox and clean installed Avast.

[jose.gimenez.47]

I did what abruptum did: https://www.youtube.com/watch?v=lFMu0UVgM24 and fixed the problem, but I´m concerned on security issues.
Is doing that all right?.
Thanks.

[Hopper15]

I did what abruptum did: https://www.youtube.com/watch?v=lFMu0UVgM24 and fixed the problem, but I´m concerned on security issues.
Is doing that all right?.
Thanks.

I'm curious about that as well.

[abruptum]

I did what abruptum did: https://www.youtube.com/watch?v=lFMu0UVgM24 and fixed the problem, but I´m concerned on security issues.
Is doing that all right?.
Thanks.

I am not an expert, but I think by enabling that preference in about:config, you are "telling" Firefox to use system certificates like other browsers like IE,Chrome etc.

[mchain]

If you write down and save your setting changes as you make them, you should be able to revert.

Having said that, I looked and found security.roots here was set to false.  Do not need to change.  No certificate errors.