-
-
Notifications
You must be signed in to change notification settings - Fork 188
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
Current Windows 11 sees ffsend as a severe trojan? #164
Comments
I am in the same situation as this issue. I ran |
An explanation of this would be nice. From the Releases page, I downloaded both executables and scanned them on VirusTotal. The version of ffsend installed with
Based on the build YML, the static and dynamic EXEs are built almost entirely the same way. And based on Rust documentation and project notes, the static library is the more reliable one. As a workaround for now, downloading and using the dynamic ffsend library should be fine. I already have a local folder called |
The project is fully open source, and clearly has no malicious function. That's easily verifiable. I'm not sure why some of these scanners see the static binary as malicious. Some of the static bits may match up with patterns in other, actually malicious, binaries. I don't know. I don't have a Windows machine to test this on though. Nor do I want to invest time in fighting against all these anti malware providers. If you're unsure about this, I recommend to review the source code and compile from source. |
Obviously a false positive but why would this happen?
The text was updated successfully, but these errors were encountered: