Hello,
For one software I compile with fpc, Avast always complained. But only when
compiled for debugging.
That exe was sent to the false positive departement, and it toke about _one mounth_ to have a corrected
version of the AV. Afterwhat, he never complained even with reworked source code.
Cheers, Ched
Le 13.02.21 à 12:02, Marco van de Voort via fpc-pascal a écrit :
Op 2021-02-12 om 22:48 schreef James Richters via fpc-pascal:
The problem I have had is when programs I compile generate a false virus detection.. sure on my own
computer I can just disable that directory from the virus scanner but it becomes a problem when I
release it to my customers and their virus scanners quarantine it. I have no idea how to register a
legitimate program as not having a virus. I've had this issue before but managed to track down the
section of code that caused it... after a completely exhaustive search.
Some tips:
- don't use debug builds.
- sign the binary, even if just selfsigned. Provide as much context to the OS (icon and the rest in
that screen). Minimalistic binaries seem to be more suspect.
- use a well known installer package, and insist on using installers. Copied
exes are also more suspect.
- unfortunately, some wellknown Delphi libraries like Indy and Zeos sometimes
trigger also.
There is no real failsafe solution. It is all hedging and hoping.
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
