Articles de support WithSecure Business Suite

Warning message of "This installer version is going to be obsoleted at the end of year 2024" during the installation of Linux Security 64
La mise à jour des définitions de programme malveillant sur un client isolé à l'aide de fsaua-update_32.exe échoue avec le message ERREUR : le fichier d'archive de mise à jour est endommagé
La mise à jour des définitions de programme malveillant sur un client isolé à l'aide de fsaua-update_32.exe échoue avec le message ERREUR : le fichier d'archive de mise à jour est endommagé
Where can I find the key code for the latest version of my Business Suite software?
Erreur : « Le code clé que vous avez saisi n'est pas valide » lors de la tentative d'exportation d'un package d'installation pour Client Security ou Server Security
"capricorn-linux64" channel are added in product's database after Linux Security 64 update version 12.0.482 and Atlant update version 1.0.319
Comment programmer Business Suite Software Updater pour installer automatiquement les mises à jour sur les appareils ?
Les services f-secure-baseguard ont disparu pour Linux Security 64 et Atlant après la mise à jour FSBG 1.0.907
How to hide the real-time scanning exclusions or other exclusions from users in the local Client Security or Server Security user interface?
WithSecure Client Security or Server Security Web content control is not blocking categories that are set as "Disallowed"

Hanging processes with Linux Security 11.00 on RHEL/CentOS 7.x

Hanging processes with Linux Security 11.00 on RHEL/CentOS 7.x

Symptoms

Linux Security 11.00 on RHEL/CentOS 7.x causes processes to hang when on-access scanning is turned on. The system log warns about one or more processes being blocked for more than 120 seconds.

Diagnosis

The Linux kernel version (3.10) used by RHEL/CentOS 7.x suffers from a subtle but serious bug that has been fixed in later kernel versions.

Specifically, the function fanotify_merge() has a faulty logic that replaces fsnotify_event when test_event->refcnt is 2. The original test_event is replaced with a clone and then removed from the notification queue. If the original test_event was carrying an OPEN_PERM event, it has no chance of being woken up again because only the clone of the event will get a response.

Solution

The bug has been fixed in RHEL/CentOS 7.x. Simply run

yum update

to get a current kernel (3.10.0-327.36.1.el7 or later) and reboot.