Categories to Whitelist/Blacklist by:
Having the option to allow or block by these categories would make things easier for certain programs that don’t retain the status when updating or that Glasswire doesn’t recognize as an updated version of the same program.
Thanks for the feedback, I’ll share this with the team. Maintaining firewall rules when apps update is something we’ll be looking into soon as part of our ongoing firewall improvements.
Thanks again for taking the time to share your thoughts.
1 Like
It really needs to use a “fingerprint” which is based on vendor (code signing cert), app/process name, and file path (with wildcards). This combination should minimise false matches with unrelated or even rogue apps.
1 Like
This is a good idea. I was thinking somewhere along these lines or having the option to customize/override the settings on a bulk/individual basis.
Yeah, we have been requesting this (and has been promised) for many years now.
I suspect part of the problem is providing enough configuration options to make it safe and reliable, whilst maintaining ease of use.
GlassWire have been collecting telemetry data for years and so should be able to provide some user-friendly pre-set smart rules for many of the common apps. Then they just need to include the ability for more advanced users to create custom rules.
1 Like
Whitelist and blacklist control by vendor or application name would definitely improve long-term rule management. Many applications change file paths or hashes after updates, which causes unnecessary re-approval. Category-based handling would solve that gap nicely.
1 Like