Installing F-Secure Linux Security 11 and Policy Manager for Linux 12 on the same server

This article provides information on installing the F-Secure Linux Security 11 and Policy Manager for Linux 12 on the same server.

Limitations and compatibility issues

By default, firewall in Linux Security (LS) will block ports 8080 and 8081 used by Policy Manager (PM). Allowing the services in LS WebUI works, but also overrides the firewall rules locally from now on. This means that they cannot be set anymore from PM Console but only from LS WebUI.
F-Secure Automatic Update Agent (FSAUA) will be installed by both products. This will not affect the functionality per se, but uninstalling the second package by using package manager (rpm/dpkg) will most likely fail due to the files being already deleted. Use "rpm -e --justdb --nodeps --noscript" or similar to clean up the package database.

Installation on a new server environment

Install Linux Security 11 in standalone mode by using the nofirewall installer option.
Stop FSAUA:
```
 /etc/init.d/fsaua stop
```
.
Install the fspmaua package by using
```
rpm/dpkg
```
.
Install the fspms package by using
```
rpm/dpkg
```
.
Run the following command:
```
/opt/f-secure/fspms/bin/fspms-config
```
and select no for using the existing FSAUA configuration as the basis. Other choices can be left to default values.

Configure Linux Security to managed mode:

/opt/f-secure/fsav/fsav-config --auto managed fspms=http://XX.XX.XX.XX/ adminkey=/path/to/admin.pub nofirewall

Install the PM Console package on the same server or on a separate machine.

Upgrading a product or using existing installations

The product upgrades are not supported when installing on the same server. We recommend a clean installation when upgrading a product.

Technical discussion

PM takes over the FSAUA configuration. LS does not fetch updates from PM nor from a public server but picks the updates directly from the FSAUA data directory (/var/opt/f-secure/fsaua/data/content/) by using fsupdated.