Hi Martin, On Thu, Oct 11, 2012 at 5:42 PM, Martin Zibricky <[email protected]>wrote:
> claudio canepa píše v Čt 11. 10. 2012 v 17:01 -0300: > > Probably a solution for run.exe would be more robust that the one they > > developed for cdpedia.exe > > Hi claudio, > > as I mentioned in http://www.pyinstaller.org/ticket/603, Thanks for the link, I searched the issue tracker by 'antivirus' and found nothing. > making run.exe > to comply with Windows Data Execution Prevention could be more robust > fix. I need to find some guidelines how to do that. > > It would be bummer to research 'Windows Data Execution Prevention' to find its not relevant. I was not trying to run my executable nor pyinstaller run.exe, the alerts come from a scan. I cannot point to exact wording, but the mention of specific threat name usually comes from signature analysis. Heuristic code analysis usually flags 'suspicious something in file zzz' For a Windows Data Execution Prevention problem I would expect a OS MsgBox telling something, not an AV alert. Probably you can get better info to attack the false positive problem directly from AVG, and given the fast response time I got, something worth to try. Not telling you are wrong, but its feel to me like in premature optimization: going to suspected problems before problem confirmation. cheers -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
