Profile based on files' fingerprint

[PhilJbt]

What would you like to add or change?:
To prevent a file (i.e. an executable on Windows) from gaining network access by replacing another legitimate file, the profile linked to a file should keep its fingerprint (e.g. a simple CRC-32 hash).
If the fingerprint of a file doesn't fit the stored one, Portmaster could warn the user of the situation and ask if the profile's rules needs to be reset, or the stored fingerprint to be updated.

Why do you and others need this?:
Beyond the fact that unusual behavior might be easier to detect when knowing a file has just been modified, the fact that a malicious file can replace a previously validated one is a security issue (on Windows in particular, both with regard to third-party programs and built-in services).

[github-actions]

This issue has been automatically marked as inactive because it has not had activity in the past two months.

If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.

[github-actions]

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.

If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord.