You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does anybody understand, why a DBF file (dBase) is marked as executable. I've already tried to enhance the filerules (application/octet-stream which should work), but no success.
allow text - -
allow \bscript - -
allow archive - -
allow postscript - -
allow application/octet-stream - -
allow application/zip - -
allow application/x-zip - -
allow application/x-gzip - -
deny self-extract No self-extracting archives No self-extracting archives allowed
deny executable No executables No programs allowed (Type is excutable)
The text was updated successfully, but these errors were encountered:
@rightvision the binary file preamble resembles an executable. I am working on a way to override this rule by extension as it is a frequent problem. In the meantime you can alternatively create a ruleset and remove that deny rule based on your ruleset criteria.
Does anybody understand, why a DBF file (dBase) is marked as executable. I've already tried to enhance the filerules (application/octet-stream which should work), but no success.
allow text - -
allow \bscript - -
allow archive - -
allow postscript - -
allow application/octet-stream - -
allow application/zip - -
allow application/x-zip - -
allow application/x-gzip - -
deny self-extract No self-extracting archives No self-extracting archives allowed
deny executable No executables No programs allowed (Type is excutable)
The text was updated successfully, but these errors were encountered: