Author Topic: Versions 8 and lower no longer supported  (Read 12325 times)

0 Members and 1 Guest are viewing this topic.

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11773
    • AVAST Software
Re: Versions 8 and lower no longer supported
« Reply #30 on: May 15, 2020, 10:38:24 AM »
Hello there,
I noticed that after version 8 and below support was cut, mozilla firefox HTTPS traffic is not working properly.

For example, clicking on test viruses is no problem in HTTP
http://2016.eicar.org/download/eicar.com

But HTTPS does not detect traffic.
https://secure.eicar.org/eicar.com

I discussed this issue with firefox officers. The problem is a bilateral problem, but it seems to be avast.

That is, if I install with the latest 2020 setup file of avast, HTTPS detection works fine.
However, in avast version 9 and above, HTTPS traffic does not work properly.

I am satisfied with the avast 11 version, I use it.
It is noteworthy that it removes HTTPS when it uninstalls and reinstalls it, but it does not detect HTTPS scanning again when it receives VPS updates.
Apparently not only for avast 8 and below, support for 18 and below versions has been cut off, the VPS packages you provided are causing problems. This problem does not exist in versions 19 and 20. All the other sub-versions have the same problem.

HTTPS traffic runs smoothly in opera, but there is a problem in firefox. I should point out that this issue is not a simple certificate issue, but all certificates are complete.

The current 2020 version of avast with Firefox works flawlessly, but why does it not detect HTTPS traffic when the VPS update comes to other older versions?

This has nothing to do with the end of v8 support (what you noticed has actually happened much sooner) - but otherwise it's a great example of why it's necessary to use the latest versions of your antivirus.

Browsers change continuously - and sometimes they change in a way that a particular Avast feature (such as https scanning) either stops working completely, or starts causing some problems (for example, it's not possible to open specific web pages). If that happens, we update the code to resolve that - and the fix is released in the next program update. However, we don't want to cause weird problems or conflicts for people that, for some reason, don't use the latest version of Avast - so we (if possible) restrict or disable the related Avast feature for those old program versions via virus definition updates.

Offline wolf55

  • Newbie
  • *
  • Posts: 4
Re: Versions 8 and lower no longer supported
« Reply #31 on: May 15, 2020, 03:41:06 PM »
Hello there,
I noticed that after version 8 and below support was cut, mozilla firefox HTTPS traffic is not working properly.

For example, clicking on test viruses is no problem in HTTP
http://2016.eicar.org/download/eicar.com

But HTTPS does not detect traffic.
https://secure.eicar.org/eicar.com

I discussed this issue with firefox officers. The problem is a bilateral problem, but it seems to be avast.

That is, if I install with the latest 2020 setup file of avast, HTTPS detection works fine.
However, in avast version 9 and above, HTTPS traffic does not work properly.

I am satisfied with the avast 11 version, I use it.
It is noteworthy that it removes HTTPS when it uninstalls and reinstalls it, but it does not detect HTTPS scanning again when it receives VPS updates.
Apparently not only for avast 8 and below, support for 18 and below versions has been cut off, the VPS packages you provided are causing problems. This problem does not exist in versions 19 and 20. All the other sub-versions have the same problem.

HTTPS traffic runs smoothly in opera, but there is a problem in firefox. I should point out that this issue is not a simple certificate issue, but all certificates are complete.

The current 2020 version of avast with Firefox works flawlessly, but why does it not detect HTTPS traffic when the VPS update comes to other older versions?

This has nothing to do with the end of v8 support (what you noticed has actually happened much sooner) - but otherwise it's a great example of why it's necessary to use the latest versions of your antivirus.

Browsers change continuously - and sometimes they change in a way that a particular Avast feature (such as https scanning) either stops working completely, or starts causing some problems (for example, it's not possible to open specific web pages). If that happens, we update the code to resolve that - and the fix is released in the next program update. However, we don't want to cause weird problems or conflicts for people that, for some reason, don't use the latest version of Avast - so we (if possible) restrict or disable the related Avast feature for those old program versions via virus definition updates.
Thanks for the answer.
Yes, using the latest version is of course the most correct.
But is it the problem of the user that one of the basic protection features such as HTTPS scanning is disabled?
We users trust this antivirus software and continue our lives.
Do you need to constantly monitor if the antivirus is working?

If Avast cannot perform its basic feature web protection properly, are we responsible for it?

If the important shields do not work properly, then formally state that you have completely discontinued support under the latest version.

I like avast version 11 as a user, it is plain and uses few resources.

I also know that HTTPS blocked websites as a result of hard work, users closed it ...

If you are providing support, give full support and we expect that HTTPS protection will be improved soon in avast version 9 and above.

Best regards...

Online bob3160

  • Avast √úberevangelist
  • Probably Bot
  • *****
  • Posts: 44529
  • 60 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: Versions 8 and lower no longer supported
« Reply #32 on: May 15, 2020, 04:01:05 PM »
"If Avast cannot perform its basic feature web protection properly, are we responsible for it?"
If your computer is so old that it's no longer able to run the current version of Avast, is that Avast's fault?
There comes a time when an antique (your old computer) needs to be used for show not for online exposure. IMHO
Free avast! Security Seminar: http://bit.ly/2N1eaR2  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 10 Pro v20H2 64bit, 24 Gig Ram, 1TB SSD, AvastOmni 20.7.xxx, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq

Offline wolf55

  • Newbie
  • *
  • Posts: 4
Re: Versions 8 and lower no longer supported
« Reply #33 on: May 15, 2020, 05:56:01 PM »
"If Avast cannot perform its basic feature web protection properly, are we responsible for it?"
If your computer is so old that it's no longer able to run the current version of Avast, is that Avast's fault?
There comes a time when an antique (your old computer) needs to be used for show not for online exposure. IMHO
Thanks for your ideas
My computer is not very old. This computer has been running avast free for about 10 years. I am satisfied with the old 11 versions of Avast.

What saddened me was that I had researched and learned this myself, I was safe in the old 11 version.
Unfortunately, I did not know, I am learning from the forum.

If the HTTPS traffic scan in the old version does not improve, I will have to upgrade to the 2020 version or another alternative software.

Thank you for your answer.

Best regards...

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11773
    • AVAST Software
Re: Versions 8 and lower no longer supported
« Reply #34 on: May 17, 2020, 06:28:50 PM »
I was trying to describe the scenario that's happening.
1. Avast version X is released, https scanning works for the current version of the browser(s)
2. A new version of the browser is released - with internal changes that prevent Avast https scanning from working
3. Avast version X+1 is released, with updated code to make https scanning work again

There's no way to avoid that (it's happening because there's no "supported" way of scanning browser traffic, i.e. no API - so WebShield, and especially https scanning, has to rely on some internal stuff of the browsers).
So yes, Avast supports HTTPS scanning - by updating the code and releasing it as a new version.

In case you think that version 11 would somehow be updated... that's not possible, the versioning is linear. When version 11 was updated, after a few minor versions it became version 12. Then, after a few minor version, it became version 17... and now we're at version 20.3 We can't go back in time and release an update for version 11 - even if a specific problem was found affecting all versions 11 and later, the fix would be version 20.4 - with all the changes of the past few years.
In special cases it's possible to release emergency updates for a few versions back - but that is limited to small changes (which updating all the https support code for the latest browsers definitely would not be), and it certainly can't go back years old. I mean, we probably wouldn't be able to even compile those old versions, the tools have been updated many times since then. (I'm not even sure if version 11 had the emergency updater, for that matter.)

So I have to repeat again - the only way to stay as safe as possible is to use the latest versions of the program. If you stay on an older version, you are at risk that some features stop working (because of changes in 3rd party software, i.e. out of our control), the antivirus may not be effective against latest threats (of course the antivirus core responds to the latest development in the world of malware in each version - so older version may not be able to "see" some things), and you may be vulnerable to some security bugs in the antivirus itself (which again we fix once we learn them - and the fix is released as new versions).

Offline wolf55

  • Newbie
  • *
  • Posts: 4
Re: Versions 8 and lower no longer supported
« Reply #35 on: May 17, 2020, 11:20:14 PM »
I was trying to describe the scenario that's happening.
1. Avast version X is released, https scanning works for the current version of the browser(s)
2. A new version of the browser is released - with internal changes that prevent Avast https scanning from working
3. Avast version X+1 is released, with updated code to make https scanning work again

There's no way to avoid that (it's happening because there's no "supported" way of scanning browser traffic, i.e. no API - so WebShield, and especially https scanning, has to rely on some internal stuff of the browsers).
So yes, Avast supports HTTPS scanning - by updating the code and releasing it as a new version.

In case you think that version 11 would somehow be updated... that's not possible, the versioning is linear. When version 11 was updated, after a few minor versions it became version 12. Then, after a few minor version, it became version 17... and now we're at version 20.3 We can't go back in time and release an update for version 11 - even if a specific problem was found affecting all versions 11 and later, the fix would be version 20.4 - with all the changes of the past few years.
In special cases it's possible to release emergency updates for a few versions back - but that is limited to small changes (which updating all the https support code for the latest browsers definitely would not be), and it certainly can't go back years old. I mean, we probably wouldn't be able to even compile those old versions, the tools have been updated many times since then. (I'm not even sure if version 11 had the emergency updater, for that matter.)

So I have to repeat again - the only way to stay as safe as possible is to use the latest versions of the program. If you stay on an older version, you are at risk that some features stop working (because of changes in 3rd party software, i.e. out of our control), the antivirus may not be effective against latest threats (of course the antivirus core responds to the latest development in the world of malware in each version - so older version may not be able to "see" some things), and you may be vulnerable to some security bugs in the antivirus itself (which again we fix once we learn them - and the fix is released as new versions).
Thank you for your answer.