Can F-Secure Linux Security 64 be pre-installed on a virtual machine Golden image? How to reset the Unique Identifier (UID)?
F-Secure Linux Security 64 does not have the capability of changing its Unique Identifier (UID). The UID is tied to the hardware and cannot be reset, hence Linux Security 64 cannot be pre-installed on a Golden Image.
Article no: 000018034
This is the list with descriptions of the services installed for F-Secure Linux Security 64.
This information can be changed without notice.(06/Aug/2019) f-secure-baseguard-accd.service
Responsible for receiving access permission requests from the kernel through the fanotify API. It can grant access autonomously, but for malware analysis, it uses f-secure-baseguard-icap.service.
BaseGuard facility for email spam scanning. In LS64, the service is inactive.
A relic from the early days of BaseGuard. For full backward-compatibility reasons, the service cannot be removed, but it serves no purpose in any product.
Makes sure channel updates don't accumulate on the disk without limit.
The malware analysis service used for realtime, scheduled and manual scanning.
A local proxy for F-Secure's Online Reputation Service. It is used by f-secure-baseguard-icap.service.
Monitors F-Secure's GUTS2 service for channel updates and sends notifications to fsbg-updated.service.
Maintains the file integrity checker baseline.
Locally distributes policy settings to LS64 services.
Manages manual and scheduled scans.
Collects status and statistics information from LS64 services and relays them to the policy agent (fsma2)
Collects status and statistics information from BaseGuard services and relays them to the policy agent (fsma2)
Schedules the installation of online channel updates.
Locally distributes policy settings to BaseGuard services.
Article no: 000014984
What are the main differences between F-Secure Linux Security 64 and F-Secure Linux Security 11.x?
Linux Security 64 is a native 64-bit application, however there are some differences compared to the previous released version Linux Security 11.x, most notably:
no support for standalone installation mode no support for Protection Service for Business (PSB) installation mode no firewall no web user interface (for remote management with browser) no support for F-Secure Policy Manager Proxies no support for unattended (scripted) installations
The list of supported Linux distributions is also different with some legacy distributions only being supported by Linux Security 11.x. Also note, that while the installer for LS 64 is created/exported in Policy Manager Console, neither Linux Security 11 nor Linux Security 64 can be deployed/pushed to hosts using Policy Manager Console.
Article no: 000014897
The following errors are show during Linux Security 64 installation. 1:f-secure-linuxsecurity-12.0.6-1 ################################# [100%] 2019-10-21 11:15:03 net/fshttp.c:1662 idle timeout occurred 2019-10-21 11:15:03 fshttps.c:560 a timeout occurred 2019-10-21 11:15:03 fsguts2.c:1830 unable to perform the HTTP operation, error 201 (timed out) 2019-10-21 11:15:03 fsguts2.c:1062 unable to fetch update information from the server, error 201 (timed out) 2019-10-21 11:15:03 src/guts2download.c:148 unable to fetch the list of updates, error 201 (timed out) 2019-10-21 11:15:03 src/guts2download.c:84 downloading the channel content failed, error 201 (timed out) Failed to activate the product!
Make sure the Policy Manager Server is accessible by the Linux Security 64 installation target machine.
Article no: 000017159
Is SUSE Linux Enterprise Server 12 (SLES) a supported platform for F-Secure Linux Security 64?
SUSE Linux Enterprise Server 12 (SLES) has been added to the officially supported platforms for F-Secure Linux Security 64. For more details you can check the release notes on this link.
Article no: 000013134
F-Secure Linux Security 64 is not connecting to the Policy Manager Server and it is not visible in the "Import new hosts" tab in Policy Manager Console.
Verify the connection from F-Secure Linux Security 64 to the Policy Manager Server. If the issue persists, configure the address of Policy Manager Server using the server's IP address instead of hostname during the creation of the installation package.
Article no: 000016582
After installing F-Secure Linux Security 64 the following error messages related to the missing dependencies is returned.
Do you accept this license agreement? The license agreement text is available at /opt/f-secure/linuxsecurity/doc/LICENSE
/var/opt/f-secure/linuxsecurity/download/linuxsecurity-1200-linux-x86_64/1562587205/content/setup: package 'fuse-libs.x86_64' is not installed
2019-07-19 13:11:56 src/fsbootstrap.c:417 executing '/var/opt/f-secure/linuxsecurity/download/linuxsecurity-1200-linux-x86_64/1562587205/content/setup' failed, result 256
2019-07-19 13:11:56 src/fsbootstrap.c:209 install failed
Failed to activate the product!
You need to install the necessary dependencies.
Uninstall the current F-Secure Linux Security 64
rpm -e f-secure-linuxsecurity
Install the missing dependencies (example fuse-libs and libcurl)
yum install -y fuse-libs libcurl
Re-install F-Secure Linux Security 64 by using the following commands.
bash f-secure-linuxsecurity/f-secure-linuxsecurity-installer 2>&1 | tee ls64_install_2.log
Article no: 000014074
F-Secure Linux Security 64: launching a manual scan as a non-root user fails with the following error: /opt/f-secure/linuxsecurity/bin/fsanalyze: line 56: /etc/opt/f-secure/fsbg/mgmt/lock: permission denied
Running fsanalyze with a non-root user is currently not supported. We are working on providing this functionality, which will become available in a future release. Current estimate for releasing this feature is 31.10.2019 As a workaround, do the following:
Run a manual scan on the system using fsanalyze with a root account, or Configure a scheduled scan via Policy Manager Console
You can also use Linux Security 11.10, which has support for manual scanning using fsav (5) even for non-root users. Linux Security 11.10 is still supported until 31.12.2020.
Article no: 000015618