Hi Gregory.
We're glad to clarify this.
We'll certainly answer your concern.
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 (the most transparent way, as opposed to other mechanisms that are available, like simply blocking QUIC traffic and let the browser handle it).
However, once you, the user, disable QUIC scanning - we will ignore such connections completely and won't block QUIC inside browsers (and remove the policy from the registry).
I did not give AVG permission to make Chrome "Managed by your Organization". How do I get rid of this?
Hi Gregory.
We're glad to clarify this.
We'll certainly answer your concern.
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 (the most transparent way, as opposed to other mechanisms that are available, like simply blocking QUIC traffic and let the browser handle it).
However, once you, the user, disable QUIC scanning - we will ignore such connections completely and won't block QUIC inside browsers (and remove the policy from the registry).