Integrity Checking - F-SECURE LINUX SECURITY Manual

70 | F-Secure Linux Security | Troubleshooting
My network stopped working after I upgraded the product, how can I fix this?
You have to upgrade the MIB file in your F-Secure Policy Manager installation, otherwise the
upgraded product uses the Server firewall profile, which blocks virtually all traffic.

Integrity Checking

Troubleshooting issues with the integrity checking feature.
Symlinks are not working for Integrity Checking or Rootkit Protection, what can I do?
You may be denied to load a kernel module if the file containing the kernel module is a symlink
and the real file where the symlink points to is not in the Integrity Checking baseline. The same
applies if modprobe or insmod utilities (the module loaders) use files or libraries which are
symlinks and the file where the symlink points to is not in the baseline.
For example, modprobe uses /lib/libz.so.1, which is really a symlink to a real file
/lib/libz.so.1.2.2. The symlink is in the baseline but the real file is not. In this case,
modprobe is not allowed to run as it tried to open a file that is not in the baseline.
You should never add only symlinks to the baseline, you should always add both the symlink
and the real file where the symlink points.
I forgot to use Software Installation Mode and my system is not working properly. What
can I do?
Create a new baseline. Execute the following commands:
/opt/f-secure/fsav/bin/fslistfiles | fsic --add -
fsic --baseline
Can I update the Linux kernel when I use Integrity Checking?
Use the Software Installation Mode. After you have updated the kernel, disable the Software
Installation Mode to restore the normal protection level.