In this section
•List of Supported Operating System Versions
•Additional Packages and Components
•Compatibility with Security Subsystems
You can use Dr.Web for UNIX File Servers on a computer that meets the following requirements:
Component |
Requirement |
|---|---|
Platform |
Processors of the following architectures and command systems are supported: •Intel/AMD: 32-bit (IA-32, x86); 64-bit (x86-64, x64, amd64) •ARM64 •E2K (Elbrus) •IBM POWER (ppc64el) |
RAM |
At least 500 MB of free RAM (1 GB or more is recommended) |
Free disk space |
At least 2 GB of free disk space on a volume where the product directories are located |
Operating system |
GNU/Linux (based on kernel version 2.6.37 or later, using glibc library 2.13 or later, systemd initialization system ver. 209 or later), FreeBSD. The supported operating system versions are listed below. The operating system must support the PAM authentication mechanism |
Other |
The following valid network connections: •valid Internet connection to enable updates for virus databases and Dr.Web components; •when operating in the centralized protection mode, connection to the server on the local network is enough; connection to the Internet is not required |
To ensure the correct operation Dr.Web for UNIX File Servers, open the following ports:
Purpose |
Direction |
Port numbers |
|---|---|---|
To receive updates |
outgoing |
80 |
To connect to the Dr.Web Cloud service |
outgoing |
2075 (including those for UDP), |
List of Supported Operating System Versions
•GNU/Linux
Platform |
Supported GNU/Linux versions |
|---|---|
x86_64 |
•Astra Linux Special Edition 1.5 (with cumulative patch 20201201SE15), 1.6 (with cumulative patch 20200722SE16), 1.7 •Astra Linux Common Edition (Orel) 2.12 •Debian 9, 10 •Fedora 31, 32 •CentOS 7, 8 •Ubuntu 18.04, 20.04, 22.04 •ALT Workstation 9, 10 •ALT Server 9, 10 •ALT 8 SP •RED OS 7.2 MUROM, RED OS 7.3 MUROM •GosLinux IC6 •SUSE Linux Enterprise Server 12 SP3 •Red Hat Enterprise Linux 7, 8 |
x86 |
•CentOS 7 •Debian 10 •ALT Workstation 9, 10 •ALT 8 SP |
ARM64 |
•Ubuntu 18.04 •CentOS 7, 8 •ALT Workstation 9, 10 •ALT Server 9, 10 •ALT 8 SP •Astra Linux Special Edition (Novorossiysk) 4.7 |
E2K |
•Astra Linux Special Edition (Leningrad) 8.1 (with cumulative patch 8.120200429SE81) •ALT 8 SP •Elbrus-D MCST 1.4 •GS CS Elbrus 8.32 TVGI.00311-28 |
ppc64el |
•CentOS 8; •Ubuntu 20.04 |
|
In ALT 8 SP, Astra Linux Special Edition (Novorossiysk) 4.11, Elbrus-D MCST 1.4 and GosLinux IC6 mandatory access control is not supported. |
For other GNU/Linux versions that meet the abovementioned requirements full compatibility with Dr.Web for UNIX File Servers is not guaranteed. If a compatibility issue occurs, contact technical support.
• FreeBSD
Platform |
Supported FreeBSD versions |
|---|---|
x86 |
11, 12, 13 |
x86_64 |
11, 12, 13 |
|
For FreeBSD OS, Dr.Web for UNIX File Servers can be installed only from the universal package. |
Additional Packages and Components
Dr.Web for UNIX File Servers does not require installation of additional packages and OS components (except for the protected server software, see below).
|
For convenient work with Dr.Web for UNIX File Servers in the command line, you can enable command auto-completion in your command shell (if disabled).
If you encounter any problem with installation of additional packages and components, refer to the documentation of your operating system version. |
•Operation of SpIDer Guard in the operating system kernel mode (LKM module) is not supported for operating systems launched in the Xen hypervisor environment. An attempt to load the SpIDer Guard kernel during the OS operation in the Xen environment can lead to a critical error of the OS kernel (so called “Kernel panic” error).
•Operation of SpIDer Guard in the operating system kernel mode (LKM module) is not supported for ARM64 and E2K architectures.
•SpIDer Guard can operate in the enhanced (Paranoid) mode, which blocks access to the files that have not been scanned yet, only via fanotify and providing that an OS kernel is built with the enabled CONFIG_FANOTIFY_ACCESS_PERMISSIONS option.
1.Samba File Service
For integration with Samba file service, the installed and configured file server Samba is required (supported Samba versions 3.6–4.16).
|
The SpIDer Guard for SMB monitor of Dr.Web for UNIX File Servers uses a special VFS SMB module for the integration with the Samba server. With the SpIDer Guard for SMB component, several versions of this module are supplied. They are built for various versions of Samba. However, the supplied versions of the VFS SMB module may be incompatible with the version of Samba installed on your file server. It may occur, for example, if your Samba server uses the CLUSTER_SUPPORT option. If VFS SMB modules are incompatible with your Samba server, the corresponding message is shown during the Dr.Web for UNIX File Servers installation. In this case, build the VFS SMB module for your Samba server manually (including the compatibility with the CLUSTER_SUPPORT option if necessary). The procedure of building the VFS SMB module from the supplied source code files is described in the Building the VFS SMB Module section. |
2.NSS File Service
For integration with NSS file service, the installed and configured Novell Open Enterprise Server SP2 based on the operating system SUSE Linux Enterprise Server 10 SP3 or newer (11 SP1, SP2) is required.
Compatibility with Security Subsystems
By default, Dr.Web for UNIX File Servers does not support SELinux. In addition, Dr.Web for UNIX File Servers operates in reduced functionality mode in the GNU/Linux systems that use mandatory access models (for example, in systems supplied with the PARSEC mandatory access subsystem that appends different privilege levels to users and files).
If installation of Dr.Web for UNIX File Servers is required for systems with SELinux (as well as for systems that use mandatory access models). It is necessary to execute additional settings of a security subsystem so that Dr.Web for UNIX File Servers operates in full functionality mode. For details, refer to the section Configuring Security Subsystems.