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
{{ message }}
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.
Shortly after updating to Filtration 1.2.1 from v1.2.0 via the built-in self-update, BitDefender "detected potentially malicious behavior and blocked all applications involved." In particular, it quarantined Filtration\Filtration.exe and Filtration\app-1.2.1\Filtration.exe (and my desktop link), each flagged with threat name "Atc4.Detection".
The text was updated successfully, but these errors were encountered:
There's a post here about another app using Squirrel triggering the same detection: FreeTubeApp/FreeTube#104
That post does say that it's caused by the executable not being signed, but unless anyone can point me at a Code Signing cert provider that doesn't cost $100/year then unfortunately I'm not going to be able to code sign Filtration.
I think all I can suggest for now is that you manually exclude the C:\Users\<username>AppData\Local\Filtration directory from BitDefender's scanning.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Shortly after updating to Filtration 1.2.1 from v1.2.0 via the built-in self-update, BitDefender "detected potentially malicious behavior and blocked all applications involved." In particular, it quarantined Filtration\Filtration.exe and Filtration\app-1.2.1\Filtration.exe (and my desktop link), each flagged with threat name "Atc4.Detection".
The text was updated successfully, but these errors were encountered: