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
windows PyInstaller-3.3.1.tar.gz -> win32/tiggre!plock #3157
Comments
Hello.
Please contact the AV-vendor and let them know this is a false alert and
have them fix it.
Thank you.
…On Thu, Dec 28, 2017 at 11:52 PM, pavelek ***@***.***> wrote:
installing / updating via pip or downloading from webpage pyinstaller
v.3.3.1 rise virus windows devenfer alert (win32/tiggre!plock)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3157>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/ARqB6ScZtRcBdgd1RLR38tizonGzh-0dks5tFBuUgaJpZM4ROtZL>
.
|
i am experiencing the same issue, but only in my python 2.7 conda environment. It works in the base python 3.6 environment. When i try to extract the local\temp\PyInstaller-3.3.1.tar.gz i get a warning from Windows Defender it thinks the archive has a Trojan (win32/tiggre!plock) |
Please contact you anti-virus vendor. There is nothing we can do about this false positive. If your anti-virus vendor considers one of the files included in the PyInstaller distribution or a file generated by PyInstaller to be malicious, there is nothing we can do about this. Even if we'd change our code, they'd change their pattern and the race starts again. See this mailing-list thread and other tickets for his topic. |
Just another data point: I am experiencing this problem as well after updating from PyInstaller 3.3 to 3.4. I'm using Python 3.5. I wrote a blog post about the issue. I submitted my app to Windows Defender as a false positive, via their online form. Hopefully this will help. |
installing / updating via pip or downloading from webpage pyinstaller v.3.3.1 rise virus windows devenfer alert (win32/tiggre!plock)
The text was updated successfully, but these errors were encountered: