Hi James,
This isn't the experience we want you to have. Let us attempt to clarify this for you.
There is a network protocol currently in development called QUIC.
As it is in the active development by Google and others, there are some versions of this protocol that we cannot check properly for malicious traffic.
Therefore, we decided to block these protocol versions and the way how we do it is using Chrome Policy setting (which is, according to Google, the preferred way to do it).
You can check the policy by visiting chrome://policy
We plan to change the behavior of the QUIC scanning. For the period of time until a full blown scanning is released in AVG, we will continue to provide security of the connections by blocking QUIC in google by the policy. However, once you, disable QUIC scanning - we will ignore such connections completely and won't block QUIC inside browsers (and remove the policy from the registry).
Thank you for your understanding in advance!
I have recently gotten a creepy "Managed by your Organization" notification on my browser.
I have been trying different searches for a solution and it comes back to something that AVG / AVAST has done which causes certain Chrome users to become vulnerable. According to other posts, you folks are already aware of the issue.
Do you have a timeline when this will be corrected? Or do you recommend I temporarily remove AVG from my system? Rely on MS Defender while you sort this vulnerability out?
Appreciate your response.
Hi James,
This isn't the experience we want you to have. Let us attempt to clarify this for you.
There is a network protocol currently in development called QUIC.
As it is in the active development by Google and others, there are some versions of this protocol that we cannot check properly for malicious traffic.
Therefore, we decided to block these protocol versions and the way how we do it is using Chrome Policy setting (which is, according to Google, the preferred way to do it).
You can check the policy by visiting chrome://policy
We plan to change the behavior of the QUIC scanning. For the period of time until a full blown scanning is released in AVG, we will continue to provide security of the connections by blocking QUIC in google by the policy. However, once you, disable QUIC scanning - we will ignore such connections completely and won't block QUIC inside browsers (and remove the policy from the registry).
Thank you for your understanding in advance!