I have an issue with exclusions in the filesystem shield.
I have the following exclusion in the webinterface (yes, its saved):
C:\Windows\assembly\Nativelmages_v4.0.30319_32\protonic.ea8c684a67#*
But, every client still blocks:
C:\Windows\assembly\NativeImages_v4.0.30319_32\protonic.ea8c684a67#\eec8f2ee13735ef64840f618b2ebe6fa\protonic.easyjob.Resources.ni.dll
The number eec8f2ee13735ef64840f618b2ebe6fa changes with updates, so cant include that in filepath.
What to do?
Try adding to the global exclusions instead of just the filesystem shield, see if it makes a difference.
But looking at it from a different angle, what indication do you have that it is blocked? Perhaps we should discover why it is blocked in the first place, since I think that’s just .NET stuff in there and shouldn’t be blocked unless it is truly malicious
Maybe being a .NET thing it is not handled in the same way as a “file”. I’d maybe ask tech support on this one…