Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

IPDefend Toolkit plugin

(1/2) > >>

comsytec:
Announcing new IPDefend Toolkit plugin 2.0.0 release. See at http://www.comsytec.com/ipdefend.php

MortenMacFly:

--- Quote from: comsytec on August 22, 2012, 10:05:36 am ---Announcing new IPDefend Toolkit plugin 2.0.0 release. See at http://www.comsytec.com/ipdefend.php

--- End quote ---
BTW: Are you aware that the binary tools are flagged as viruses by quite some AV scanners (try i.e. with virustotal)? Maybe you shouldn't use runtime-packers if not needed.

comsytec:

--- Quote from: MortenMacFly on August 22, 2012, 09:35:33 pm ---BTW: Are you aware that the binary tools are flagged as viruses by quite some AV scanners (try i.e. with virustotal)? Maybe you shouldn't use runtime-packers if not needed.

--- End quote ---
We have not scanned it by neither of AV scanners. But what happened recently to us, the GCC build from source everytime failed in mingw's shell. At that time we used ESET NOD32. We must get rid of it. NOD32 always reported some part of GCC code built from source as virus. This file was named conftest.exe much times generated by the configure to check prerequisites. We have sent an e-mail to VIRUS BULLETIN about our discovery while NOD32 is many times marked as the best AV scanner on the market. Are you interested about this article ?

This plugin is digitally signed by legal signature.

MortenMacFly:

--- Quote from: comsytec on August 23, 2012, 09:28:48 am ---Are you interested about this article ?

--- End quote ---
No thanks, I am hit by this myself often enough, too. 100% of the time its false alarm, but surely "nobody" will trust you. So from my experience I can tell that your files are most likely flagged by AV due to a runtime-packer. If you can use another one or none you may get rid of this in general. Even if you report to AV companies (there are many!) for one version of your tool in 90% of the cases you would need to do this again all the time you publish a new version, as the signature has changed. So for me, this wasn't be a good solution.

By the way: For me, a regular check with http://www.virustotal.com before a release helped to avoid such issues in most cases.

If you find a better solution - then I would be interested in.

comsytec:
Do you expect zero detection ratio ?

Navigation

[0] Message Index

[#] Next page