VSEL 2.0.3 and Github canton7/Bitpacker

[bandit61]

For office-work we are all on a windows-network, but we have a

small development-department using linux. Their pc's are using

VSEL 2.0.3.29216 Agent 5.0.4.470 and Engine 5800.7501 or

already 5900.7806.

They are expecting a strange behaviour creating packages for

linux-pc in that way, that sometimes tar.gz are no longer accessible

on the other linux-pc, or they can't create a package using the

bitpacker at all.

My linux-knowledge  is poor/small, can survey the pc's over the ePo-

console and update them. The error is reproducable at least.

Does any of you using VSEL having similar problems?

Are their process-exceptions in VSEL?

Could post vsel-policies if necessary, their are some exceptions, but

as far as i know, nothing concerning processes like creating packages.

We set them up together with the dev-department.

Any idea or help would be appreciated.

[Hayton]

This question was posted in the wrong area.

Moved from Consumer section to Business-->Endpoint Security --> Mac & Linux Products for attention.

[aarmstro]

VSEL does not offer exceptions by Process and most likely yes the Exclusions may need to be reviewed on the install and working directories for you applications. 

I would state a better option would be ENSL 10.2 Patch 1 and the reasons are :-

ENSL does offer Process Exclusion.

ENSL 10.2 Patch 1 has a fix for GIT applications

[wouterr]

VSEL OAS policy has two important settings regarding handling of compression containers.

Advanced --> Scan inside multiple-file archives (e.g. .ZIP)    

Action --> If scanning times out

Having scan inside archives enabled while action when scanning time out is set to "Deny access to the file" will definitely cause operational impact to handling of for example *.tar.gz files.