Can I install the mosh package on the Carbon Black Enterprise Server?
This solution applies to all Carbon Black versions.
This solution explains why installing the EPEL (Extra Packages for Enterprise Linux) mosh package is not supported due to a dependency conflict. Other packages that do not have a dependency conflict could be installed.
Can I install the EPEL mosh package, or another similar package?
Note: Mosh requires non-standard CentOS base repository, so the mosh package serves as an example.
Answer: The installation of EPEL packages may or may not be allowed, which depends on existing Carbon Black dependencies. For example the mosh package could not be installed because mosh requires a specific version of protobuf, while Carbon Black also requires a specific version. The two versions would conflict, and the Carbon Black installation would be negatively affected. For example when using the yum utility to install the mosh package, a dependency issue with protobuf is highlighted:
# yum install mosh
Loaded plugins: fastestmirror, security
Loading mirror speeds from cached hostfile
---> Package mosh.x86_64 0:1.2.4-1.el6 will be installed
--> Processing Dependency: libprotobuf.so.6()(64bit) for package: mosh-1.2.4-1.el6.x86_64
--> Finished Dependency Resolution
Error: Package: mosh-1.2.4-1.el6.x86_64 (epel)
Available: protobuf-2.3.0-7.el6.x86_64 (epel)
Installed: protobuf-2.4.1-1.noarch (@CarbonBlack)
From the above output, protobuf-2.3.0-7.el6.x86_64 is needed for the mosh package to be installed. However, Carbon Black depends on the already installed package protobuf-2.4.1-1.noarch, so this package cannot be installed.