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

AVG identifies burn.exe as potential thread #5576

Closed
miracle152004 opened this Issue May 9, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@miracle152004

miracle152004 commented May 9, 2017

Bugs

If this issue is a bug:

  • Which version of WiX are you building with?

3.10.3.3007

  • Describe the problem and the steps to reproduce it.

Since today the burn.exe and the wix-setup (already installed and displayed on programs and features) are identified as potential threads by AVG on our build server.
Since both files are not digitally signed our working theory is currently that it is identified because the files are not digitally signed.
The installed version of AVG is AVG Antivirus Business Edition 16.151.8013
AVG Framework Version 1.143.2.51391
AVG Setup Version 1.143.2.51391
Virus Database: 4776/14454 (09.05.2017, 3:02)

  • Describe the behavior you expected and how it differed from the actual behavior.

Both files should not be identified as potential trojan/virus.

@robmen

This comment has been minimized.

Show comment
Hide comment
@robmen

robmen May 9, 2017

Member

Please submit a false positive here: https://secure.avg.com/submit-sample

The more customers that report it the faster they will recognize the false positive.

Member

robmen commented May 9, 2017

Please submit a false positive here: https://secure.avg.com/submit-sample

The more customers that report it the faster they will recognize the false positive.

@miracle152004

This comment has been minimized.

Show comment
Hide comment
@miracle152004

miracle152004 May 9, 2017

Sorry I do not think this is the correct response.
I think this would not have happend if the tools and the setup would have been digitally signed.
And I would like a little more support on this end than "Send a false positive report".

miracle152004 commented May 9, 2017

Sorry I do not think this is the correct response.
I think this would not have happend if the tools and the setup would have been digitally signed.
And I would like a little more support on this end than "Send a false positive report".

@robmen

This comment has been minimized.

Show comment
Hide comment
@robmen

robmen May 9, 2017

Member

We do digitally sign our builds. If it isn't digitally signed then maybe you do have a counterfeit infected file.

Member

robmen commented May 9, 2017

We do digitally sign our builds. If it isn't digitally signed then maybe you do have a counterfeit infected file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment