-
Notifications
You must be signed in to change notification settings - Fork 241
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
Trojan in current windows installer? #112
Comments
Unfortunately some anti-virus software detect a false positive with this windows installer file, as is sometimes the case with files created with pyInstaller. I created the 0.4.0 windows version so that it is compatible all the way back to Windows XP. This means using older versions of PyInstaller that unfortunately seem to have this false positive identification that can cause undue concern. If you are uncomfortable running from the windows installer, then you can instead opt to Run Manuskript from Source Code on Windows. Note that these steps install the same versions of software that I used to create the windows installer. @olivierkes would you be able to add this false positive identification note to the 0.4.0 windows version as you did with the 0.3.0 one? |
Thanks for the quick response. I didn't see that this was an issue with an older version, so thought I would bring it to your attention. |
@sanjodito we appreciate receiving your report. Other users may also encounter this issue and at least now they can view this issue to learn about the false positive identification. |
Thanks for that. I reported it on the website's download page with a link to this issue. |
I downloaded the windows zip file of version 0.4.0 today from the Manuskript website and upon extracting it, McAfee immediately quarantined 5 objects as a Trojan. I can only see a partial output of the quarantine information, but it shows "Detected as: Artemis!0D40325EC..." I don't know if that was the file name or the signature that it detected, however, as I can't view the full log.
The text was updated successfully, but these errors were encountered: