Open medzernik opened 3 days ago
Thanks for opening your first issue at git-cliff! Be sure to follow the issue template! ⛰️
Sorry I'm not familiar with FSecure or why this might have happened. Can you provide more details about that report? I'm trying to understand if there is something actionable here.
The best course of action is to provide FSecure the executable and communicate with them to excempt it. It's a garbage AV app, but corporates like to use it :/ Best the author does the validation tho, attaching a screen of the detection
I think it doesn't like libZ (this happens during compilation). I'd still doublecheck, but if it's just libZ then I can move the report to libZ themselves.
Is there an existing issue for this?
Description of the bug
FSecure classifies the software as malware through heuristic analysis.
Steps To Reproduce
Use an FSecure endpoint antivirus. Download and compile/install the software.
Expected behavior
FSecure is informed of the cleanliness of the software
Screenshots / Logs
No response
Software information
Additional context
No response