Fixed issues in the Linux agent
Linux
agentFixed in Linux agent version 3.1.1001
Linux
agent version 3.1.1001When the PID number of a process was greater than 32768, a violation that was related to that process was not detected. The fix is also available using driver package version 3.1.1101 for devices running agent 2.1.1590 and later. (EPP-3214) |
Fixed in Linux agent version 3.1.1000
Linux
agent version 3.1.1000When you tried to scan a specific directory that had Japanese characters in its name using the command line option, the scan was not successful. (CHP-8700) |
Fixed in Linux agent version 3.0.1005
Linux
agent version 3.0.1005When the CylancePROTECT driver was extracted from the .tar archive, the folder permissions were unexpectedly changed. The permissions are no longer changed and the folder’s original permissions are now properly retained. This issue is fixed in the 3.0.1005 and 3.0.1105 Linux drivers. (EPP-2359) |
The deployment of CylanceHYBRID on a host computer was not successful if CylancePROTECT was running with the memory protection policy enabled. (CHP-8676) |
High memory usage was identified on Linux devices. This issue is fixed in the 3.0.1005 and 3.0.1105 Linux drivers. (CHP-8661) |
If SELinux was disabled after the CylancePROTECT drivers were already loaded, a system kernel panic error occurred. This issue is fixed in the 3.0.1005 and 3.0.1105 Linux drivers.(CHP-8651) |
Fixed in Linux agent version 3.0.1001
Linux
agent version 3.0.1001There was excessive logging of CefRPCServerHelper:listenForRequests: Error receiving message from queue using conn=## errno=110 (Connection timed out) in the system logs. For more information visit support.blackberry.com and read KB 93972. (EPP-2239) |
When trying to update or uninstall the CylancePROTECT agent, it stopped responding if any netcore application was running. (EPP-2172) |
Fixed in Linux agent version 3.0.1000
Linux
agent version 3.0.1000There are no fixed issues in this release. |
Fixed in Linux agent version 2.1.1590
Linux
agent version 2.1.1590There are no fixed issues in this release. |