What AV do you use?Sr , i enable WFP but i can't login https web . WFP not as good as 5.xxx .
New version very good. Thanks
This feature is planned.Good to see the Stealth Mode
Still would like to see I can set my own user agent. Until that is not implemented the user agent should be randomized and not just (e. g. changing browsers, nothing against Linux xD):
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.89 Safari/537.36
We'll start adding languages after beta release.Sadly no translation included yet even though available
I'm using EsetWhat AV do you use?
---------- Post added at 09:43 PM ---------- Previous post was at 09:41 PM ----------
This feature is planned.
We'll start adding languages after beta release.
ESET's NOD32/Smart Security is incompatible with Adguard's WFP driver (like Kaspersky is too) - the only workaround is to use the default TDI driver (which is what Adguard defaults to if it detects ESET/Kaspersky running). Which also means if you're using Windows 10, no filtering for Edge is possible while using ESET (or Kaspersky) and the TDI driver.I'm using Eset
With these, I assume the Bitdefender WFP issue *should* be fixed?+ New network drivers
+ New content injection algorithm (IMPORTANT: compatibility with antiviruses is not yet tested)
YES! Will this also remove any existing certificates in Firefox? I noticed in the past that I've had to manually remove the old certificate(s) from Firefox when doing a manually certificate reinstall. Same with uninstalling Adguard, it never removed the leftover certificate(s) from Firefox (had to remove manually).+ Reinstall Certificate button (https://github.com/AdguardTeam/AdguardForWindows/issues/80)
Now no need in manual stop/delete of some folders to recreate AG certificate. Adguard will automatically close all browsers, generate and import new certificate.
Great, I'll re-enable QUIC in Chrome. Which kinda reminds me... what's the latest on updating the cipher suite since the last attempt? Was the issue where Google pages were slow to load in Chrome ever tracked down?* Fixed IPv6/QUIC issue (no filtering in Chrome when QUIC over IPv6 is used)