Skip to content
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

FSecure classifies as malware #965

Open
1 task done
medzernik opened this issue Nov 26, 2024 · 3 comments
Open
1 task done

FSecure classifies as malware #965

medzernik opened this issue Nov 26, 2024 · 3 comments
Labels
question Further information is requested

Comments

@medzernik
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

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

  • Operating system: Windows 10
  • Rust version: up to date as of 26.11.2024
  • Project version: 2.7 compilation, 2.6.latest as winget install

Additional context

No response

@medzernik medzernik added the bug Something isn't working label Nov 26, 2024
Copy link

welcome bot commented Nov 26, 2024

Thanks for opening your first issue at git-cliff! Be sure to follow the issue template! ⛰️

@orhun orhun removed their assignment Nov 26, 2024
@orhun
Copy link
Owner

orhun commented Nov 26, 2024

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.

@orhun orhun added question Further information is requested and removed bug Something isn't working labels Nov 26, 2024
@medzernik
Copy link
Author

medzernik commented Nov 26, 2024

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

image

image
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants