Open ChinChillaSPb opened 4 months ago
You are correct, this is due to using pyinstaller to freeze and distribute so that people don't need the (complex) build environment to use pip.
We don't have the funds for a code signing certificate (nor the expertise to implement it to be honest).
Hopefully if enough people report it as a false positive the file signature will get updated, but other than whitelisting it with Windows Defender we're a bit stuck.
I can hand-on-heart assure you (and anyone else) that there is nothing sinister within the binary - the entire build process is viewable via our actions - https://github.com/LedFx/LedFx/blob/main/.github/workflows/test-build-binaries.yml
The associated .spec files for pyinstaller to ingest and use for windows binaries is https://github.com/LedFx/LedFx/blob/main/windows-binary.spec
Can confirm that this is being flagged after some kind of definitions update, because I've been using LedFx v2.0.99 on Windows 11 and didn't get any warning up until today.
Here's the scan of the binary with Virus Total: https://www.virustotal.com/gui/file/b1c5a09cc618f680db62753c40d69b0226e79b781543fa3cc0758374ceeb2d17
Not every antivirus detects it so far, personally I'm whitelisting this as suggested.
Keep up the good work! Best LED software I've ever used so far!
Latest Update Windows 10 Pro With latest Defender updates CORE 2.0.92 EXE detected as Win32/Wacapew.C!ml and wont allow run it... Probably because of python (as i can see with other github projects)