-
Notifications
You must be signed in to change notification settings - Fork 13
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
Incompatible with AV system #80
Comments
Here's the complete installation log, in case it might be of any use to you. My AV popped up dozens of warnings (I lost count) of suspicious behavior in various *.exe files.
|
There's no trojan, virus etc in the PAR::Packer distribution. |
I feared that might be the response. At least, you're aware of the issue. If I find myself needing to use PAR::Packer at some point, I'll have to find a way to tell my AV to calm down and accept this particular application. In the meantime, I'll just have to avoid trying to update it in the Strawberry Perl library. You may not be able to do anything about accidentally matching malware signatures, but you still might be able to deal with the Windows errors about being 64-bit incompatible. Let me know if you need a list of those test modules that were thus flagged. |
There are essentially 2 executables used by PAR::Packer, both compiled and linked by the Mingw64 toolchain included in Strawberry Perl
If the message is about these two, then that's on your toolchain. Now a |
Let me know if you want me to try the reinstall and record the names of executables that Windows complains are not 64-bit compatible and send them to you. It's not clear to me if you're asking for that. |
Thanks, but no thanks. I only have scant knowledge about the structure of Windows executables. If someone else wants to an analysis, they are more than welcome. |
My system (Strawberry Perl 5.38 on Windows 10) tried installing PAR::Packer 1.061 this morning, and my AntiVirus system went berserk, flagging dozens of *.exe files produced as "suspicious behavior", and quarantined them. Could you check that nothing malicious has found its way into your code? It may be that the latest update of the AV is overly suspicious of trying to run an *.exe file from within another running program, and flagging that, but it wouldn't hurt to be sure that your code produced doesn't contain a malware payload. Also, there were three or four instances that Windows flagged as incompatible format for a 64 bit system. In the meantime, I'll quarantine PAR::Packer itself from the daily update check, as I do not use it anyway.
The text was updated successfully, but these errors were encountered: