Linux Security 64 Change Log

Samuel_L

Linux Security 64 Beta Release Notes

Major Features in this Release

This is a beta release of Linux Security 64. This release introduces a new on-access scanner for continuous protection against viruses and potentially unwanted applications. In addition, Linux Security 64 features a system integrity checker for protection against unauthorized system modifications. The product also supports manual scanning of files.

Supported Platforms

Linux Security 64 supports the following Linux distributions:

• CentOS 7
• RHEL 7
• Oracle Linux 7
• Amazon Linux 2.0
• Debian 9
• Ubuntu 16.04
• Ubuntu 18.04

Dependencies

Linux Security 64 requires the following packages to be installed before installing the product:

CentOS, RHEL, Oracle Linux, and Amazon Linux

• fuse-libs
• libcurl
• python

Debian and Ubuntu 16.04

• libfuse2
• libcurl3
• python

Ubuntu 18.04

• libfuse2
• libcurl4
• python

Installation

Installing Linux Security 64 happens by first creating an installation package using Policy Manager and installing the product from the newly-created installer on the target machine.

Please, note that you will need the Policy Manager version 14.20 to be able to install and manage Linux Security 64.

1. Configure the Policy Manager Server to use F-Secure beta GUTS2 server:

   1. Log into a host with Policy Manager Server 14.20.
   2. Stop Policy Manager Server by running systemctl stop fspms.
   3. Remove everything from /var/opt/f-secure/fspms/data/guts2/.
   4. Open file /etc/opt/f-secure/fspms/fspms.conf and add -Dguts2ServerUrl=http://guts2tp.sp.f-secure.com to additional_java_args config parameter.
   5. Start Policy Manager Server by running systemctl start fspms

2. Create the installation package:

   1. In Policy Manager Console, select Tools > Installation Packages from the menu. This opens the Installation Packages window.
   2. Click import.
   3. Select Linux Security installation package you want to use and click Import.
   4. Select the imported installation package in the packages list and click Export.
   5. Specify a name and a folder for the exported zip file. A Remote Installation Wizard window will appear.
   6. Click Next.
   7. Enter your license keycode for the product and click Next.
   8. Adjust the address of your Policy Manager Server and it’s HTTP and HTTPS ports if you need and click Finish.

3. Copy the exported zip file to the Linux host in your network.

4. Install the product:

   1. Log into the Linux host as root.
   2. Make sure you have the prerequisites installed (refer to dependencies section above).
   3. Extract the zip file into an empty directory.
   4. Run the following command: bash f-secure-linuxsecurity/f-secure-linuxsecurity-installer
   5. Read and accept the license terms when prompted.
   6. After the installation process finishes, Policy Manager Console will shortly show the Linux host in Pending hosts list.

Uninstallation

You can uninstall the product from the command line.

1. Log in to the Linux host as root.
2. Run the uninstallation command:

• RHEL-based distributions: rpm -e f-secure-linuxsecurity
• Debian-based distributions: dpkg -r f-secure-linuxsecurity

Known Issues

• CSLP-3285: Manual and scheduled scanning are present on the GUI but currently are not operational. You can use the “fsanalyze” command to perform manual scanning from the command line.
• CSLP-3288: Fsdiag generation does not work from the GUI. Use the command-line tool directly on the node, instead.
• CSLP-3286: The update service currently does not generate alerts in case of failures.
• CSLP-3291: Service status and statistics are currently not displayed in the policy manager UI.
• CSLP-3289: Alerts are not mirrored in the system log.
• CSLP-3292: Specifying special files or files in /proc and /sys in manual scanning may hang the product.
• CSLP-3293: Debian-based systems are shown as "Unknown" in the Policy Manager Console.
• CSLP-3309: Uninstall leaves 'fsaccd' process running. As a workaround, kill the fsaccd main process manually.
  A re-install will fail if the process is still running.

johanh1

We will be very disappointed if you can't install and use the command line client without having a Policy Manager. What we do is install the single client and programmatically do manual command line scans on the server (then we process and store the output from the scanner). We don't need on-access or integrity checking functionality (surely this can be turned off?). I hope it will be possible to purchase single licenses like before.

NikolayT

At the moment of release, it will not be possible to use LS64 with no PM.

Soon after, it might be possible, but to prepare installer you will have to use PM at least once.

Also, we are not going to have cheap command-line only license any more, it is bad business for us. You will have to purchase Client or Server Edition.

For the use case of "just scanning", we are going to release new version of Scanning and Reputation Server/Service that can be used unattended.

johanh1

Thanks for the reply. If we have to get the PM and Server license, it doesn't matter so much, as long as we are able to use the command line client as before (i.e. turn off on-access and read stdout/stderr and exit codes from the command line client ).

Samuel_L

F-Secure Linux Security 64 RTM Release Notes

F-Secure Linux Security 64 provides an integrated, out-of-the-box security solution with strong real-time protection against viruses and potentially unwanted applications. It also includes host intrusion prevention (HIPS) functionality that provides protection against unauthorized system modifications, userspace and kernel rootkits. The solution can be easily deployed and managed using F-Secure Policy Manager.

Linux Security 64 Download

Main features in this release

• New on-access scanner for continuous protection.
• New system integrity checker for protection against unauthorized system changes.
• Support for manual scanning of files.
• Configurable automatic updates.
• Support for management using F-Secure Policy Manager.

Supported platforms

Linux Security 64 supports the following Linux distributions:

• CentOS 7
• RHEL 7
• Oracle Linux 7
• Amazon Linux 2.0
• Debian 9
• Ubuntu 16.04
• Ubuntu 18.04

Dependencies

Linux Security 64 requires the following packages to be installed before installing the product:

CentOS, RHEL, Oracle Linux, and Amazon Linux

• fuse-libs
• libcurl
• python

Debian and Ubuntu 16.04

• libfuse2
• libcurl3
• python

Ubuntu 18.04

• libfuse2
• libcurl4
• python

Installation

To install Linux Security 64, you first need to create an installation package using Policy Manager, then use that installation package to install the product on the target machine.

Note that you will need Policy Manager version 14.20 to install and manage Linux Security 64.

1. Create the installation package:
   1. In Policy Manager Console, select Tools > Installation packages from the menu. This opens the Installation packages window.
   2. Click Import.
   3. Select the Linux Security installation package you want to use and click Import.
   4. Select the imported installation package in the packages list and click Export.
   5. Specify a name and a folder for the exported zip file. A Remote Installation Wizard window will appear.
   6. Click Next.
   7. Enter your license keycode for the product and click Next.
   8. Adjust the address of your Policy Manager Server and its HTTP and HTTPS ports if necessary, then click Finish.

2. Copy the exported zip file to the Linux host in your network.

3. Install the product:
   1. Log into the Linux host as root.
   2. Make sure that you have the prerequisites installed (refer to the dependencies listed above).
   3. Extract the zip file into an empty directory.
   4. Run the following command: bash f-secure-linuxsecurity/f-secure-linuxsecurity-installer
   5. Read and accept the license terms when prompted.
   6. After the installation process finishes, Policy Manager Console will shortly show the Linux host in Pending hosts list.

Uninstallation

You can uninstall the product from the command line.

1. Log in to the Linux host as root.
2. Run the uninstallation command:
   1. RHEL-based distributions: rpm -e f-secure-linuxsecurity
   2. Debian-based distributions: dpkg -r f-secure-linuxsecurity

Known Issues

• CSLP-3319: Manual scanning cannot be invoked from Policy Manager Console.
• CSLP-3320: Scheduled scanning reports do not contain checksums of the detected files.
• CSLP-3321: Scheduled scanning reports do not contain engine names and versions.
• CSLP-3322: Command-line and scheduled scanning also applies malware actions to files that are part of integrity checker baseline.
• CSLP-3323: Manual channel updates cannot be triggered from Policy Manager Console.
• CSLP-3289: All alerts are not mirrored in the system log.
• CSLP-3327: Removing the product does not stop or remove f-secure-linuxsecurity-scand service.

etomcat

Dear Sirs,

 

I would like to understand how this tiny, 3MB sized "F-Secure 64 for Linux Security" package is able to meet or exceed the anti-virus  and other protective capabilities of the previous, almost 200MB sized "FSAV Linux Security 11.10.68" package?

 

Thanks in advance, Yours Sincerely:
Tamas Feher, Hungary.

Samuel_L

F-Secure Linux Security 64 Update 12.0.35 Release Notes

Change Log

• CSLP-3327: Uninstalling Linux Security 64 now properly stops and removes all the associated services.
• CSLP-3289: Alerts are now visible in system log.

Known Issues

• CSLP-3319: Manual scanning cannot be invoked from Policy Manager Console.
• CSLP-3320: Scheduled scanning reports do not contain checksums of the detected files.
• CSLP-3321: Scheduled scanning reports do not contain engine names and versions.
• CSLP-3322: Command-line and scheduled scanning also applies malware actions to files that are part of integrity checker baseline.
• CSLP-3323: Manual channel updates cannot be triggered from Policy Manager Console.

Samuel_L

F-Secure Linux Security 64 Update 12.0.39 Release Notes

Change Log

• CSLP-3346: Fix issue where updates were not properly registered as installed.

Known Issues

• CSLP-3319: Manual scanning cannot be invoked from Policy Manager Console.
• CSLP-3320: Scheduled scanning reports do not contain checksums of the detected files.
• CSLP-3321: Scheduled scanning reports do not contain engine names and versions.
• CSLP-3322: Command-line and scheduled scanning also applies malware actions to files that are part of integrity checker baseline.
• CSLP-3323: Manual channel updates cannot be triggered from Policy Manager Console.

Samuel_L

F-Secure Linux Security 64 Update 12.0.52 Release Notes

Change Log

• Added support for Red Hat Enterprise Linux 8 and Suse Linux Enterprise Server 12.
• Configuration changes done via Policy Manager now applied more rapidly to Linux Security 64 installations.
• Miscellaneous bug fixes.

Known Issues

• CSLP-3319: Manual scanning cannot be invoked from Policy Manager Console.
• CSLP-3320: Scheduled scanning reports do not contain checksums of the detected files.
• CSLP-3321: Scheduled scanning reports do not contain engine names and versions.
• CSLP-3322: Command-line and scheduled scanning also applies malware actions to files that are part of integrity checker baseline.
• CSLP-3323: Manual channel updates cannot be triggered from Policy Manager Console.

Sami_J

The Linux Security 64 product consists of sub-components that get software updates independently from main product updates.

To follow all the changes in the product, subscribe to the components' own change log threads:

 

FSBG (component) change log

BaseGuard (component) change log

Samuel_L

Change Log

 

• CSLP-3462: Fixed a crash in f-secure-linuxsecurity-scand.service that occurs during the scheduled scanning when scanned files have invalid UTF-8 codepoints in their file names.
• CSLP-3468: The amount of skipped files (scan errors) has been limited to 1000 in the scheduled scan report to avoid sending too long scan reports to Policy Manager.
• CSLP-3465: Removed the EULA acceptance prompt during the installation.
• CSLP-3485: Allow a regular user to run fsanalyze.

Samuel_L

New Linux Security 64 Update has been released. This update includes the following changes:

Change Log

• CSLP-3417: Decreased the number of services executed as root.

Samuel_L

New Linux Security 64 Update has been released. This update includes the following changes:

Change Log

• Added support for Debian 10 and SUSE Linux Enterprise Server 15.

Samuel_L

New Linux Security 64 installation package has been released. The new installation package adds support for using Linux Security 64 in stand-alone deployments. The new installation package requires Policy Manager version 14.30 or newer. The previous installation package is still available for users with older Policy Manager versions.

 

The new installation package can be found from the downloads page.

Samuel_L

New Linux Security 64 Update has been released. This update includes the following changes:

Change Log

• CSLP-3561: Fixed scheduled scanner issue with renaming and deleting harmful files as a non-root user in directories with the sticky bit set.
• CSLP-3356: To support isolated environments with restricted network connectivity, Linux Security 64 can now also be activated by using content stored on the file system (without downloading data over the network), and automatic product and virus definition database updates over the network can be disabled at installation time.
• Added support for Policy Manager Proxies
• Miscellaneous enhancements and bug fixes.

Known Issues

• CSLP-3651: Product installation may fail with errors about installing databases when installing the product using a content package. As a workaround, try uninstalling the product as instructed in the Uninstalling the product section of the User Guide and retry the installation.
• The offline-update program will always install all product updates immediately, regardless of any customizations made in the product configuration to the schedule for installing updates.