- Overview
- Virtual appliance system requirements
- CylanceHYBRID agent capacity
- CylanceHYBRID considerations
- Import and configure the CylanceHYBRID virtual appliance
- CylanceHYBRID Status page
- Log in to the Status page
- Status page field definitions
- Update CylanceHYBRID
- Reboot the virtual appliance
- Update SSL certificate
- Change the Certificate Cipher mode
- Export Hybrid configuration
- Change IP assignment
- Configure Active Directory
- Configure a proxy server
- Start the virtual appliance
- Stop the virtual appliance
- Change the local user account password
- Configure a Static IP using the OVF Tool
- Things to know about CylanceHYBRID agents
- Configure the BlackBerry Protect Desktop Windows agent
- Configure BlackBerry Protect Desktop macOS agents
- Configure BlackBerry Protect Desktop Linux agents
- Support article links
- Troubleshooting
- Third-party products and licenses
- Legal notice
- BlackBerry Docs
- Cylance products
- CylanceHYBRID
- Things to know about CylanceHYBRID agents
- Configure BlackBerry Protect Desktop Linux agents
Configure BlackBerry Protect Desktop Linux agents
BlackBerry Protect Desktop
Linux agentsConvert and distribute certificates
BlackBerry Protect Desktop
Agents must trust the certificate that the CylanceHYBRID
virtual appliance has been configured with to communicate with the virtual appliance. Linux Agents do not use a central certificate store like Windows or macOS systems. Instead, the Linux agent uses the certificate store from the Mono framework. These certificates must be formatted in a Mono-specific format. Once the x509 certificate is converted into the Mono format, the certificate files can be distributed to Linux endpoints. By converting the certificates, you do not need to install Mono on each
BlackBerry Protect Desktop
Linux agent endpoint.