Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test Adguard for compatibility with Dr.Web antivirus #1122

Closed
vbagirov opened this issue Jun 1, 2016 · 5 comments
Closed

Test Adguard for compatibility with Dr.Web antivirus #1122

vbagirov opened this issue Jun 1, 2016 · 5 comments

Comments

@vbagirov
Copy link
Member

vbagirov commented Jun 1, 2016

Looks like when WFP driver is selected for Adguard, Dr.Web doesn't react on webistes he normally does.

Test:

  1. If it is possible to reproduce the;
  2. Is there a way to add Adguard to filtered apps/browsers in Dr.Web? (and if so, will this solve the problem?)

Dr.Web 11 latest build, Windows 8.1

Original forum thread:
https://forum.adguard.com/index.php?threads/adguard-%D0%B4%D0%BB%D1%8F-windows-%D0%91%D0%B5%D1%82%D0%B0-%D0%B2%D0%B5%D1%80%D1%81%D0%B8%D1%8F-6-0-224-r%D0%A1.9447/page-6#post-84526

There's also a video of a problem available in this thread on drweb forum:
http://forum.drweb.com/index.php?showtopic=324792

@gshumihin
Copy link

gshumihin commented Jun 1, 2016

Issue reproduced. Adguard blocks dr.web's safebrowsing when WFP enabled. Adding dr.web to filtered apps list in adguard or adding adguard to whitelist in dr.web doesn't affect anything.

@ameshkov ameshkov added this to the 6.2 milestone Jun 3, 2016
@vbagirov
Copy link
Member Author

Specifically the Dr.Web's module in question is called 'Spider Gate' in Dr.Web Security Space.

Another forum topic is: https://forum.adguard.com/index.php?threads/adguard-%D0%B8-drweb-spider-gate.77/page-3#post-102687

@ameshkov
Copy link
Member

ameshkov commented Feb 9, 2017

@vozersky please test it with v6.1R3

@vozersky
Copy link
Member

@ameshkov Same. Reproduced with v6.1R3.

@ameshkov ameshkov modified the milestones: 6.3, 6.2 Sep 12, 2017
@ameshkov ameshkov removed this from the 6.3 milestone Oct 9, 2017
@vozersky vozersky assigned zzebrum and unassigned vozersky Feb 1, 2019
@stale
Copy link

stale bot commented Aug 1, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Aug 1, 2019
@stale stale bot closed this as completed Aug 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants