You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've already received a few reports that Windows Defender detects flowkeeper.exe as malware, e.g. #107. Those are not caught by the Defender scans that the pipeline runs as part of the release. Indeed, Defender might update its detection database after the release.
We need to implement a scheduled pipeline (ideally public, in GitHub), which runs every day and submits / rescans the latest binaries using VirusTotal APIs. Once it detects a false positive -- it should send me an email.
The results can be published as a badge on the GitHub page, and added to Downloads section on flowkeeper.org, so that the users feel safe when they install it.
We've already received a few reports that Windows Defender detects flowkeeper.exe as malware, e.g. #107. Those are not caught by the Defender scans that the pipeline runs as part of the release. Indeed, Defender might update its detection database after the release.
We need to implement a scheduled pipeline (ideally public, in GitHub), which runs every day and submits / rescans the latest binaries using VirusTotal APIs. Once it detects a false positive -- it should send me an email.
The results can be published as a badge on the GitHub page, and added to Downloads section on flowkeeper.org, so that the users feel safe when they install it.
This can be done together with #103.
Reporting false positives: https://docs.virustotal.com/docs/false-positive-contacts
Potential alternatives to VirusTotal:
The text was updated successfully, but these errors were encountered: