System Requirements and Compatibility

In this section

System Requirements

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 POWER9, Power10 (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 enable the correct operation of 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), 3010 (TCP), 3020 (TCP), 3030 (TCP), 3040 (TCP)

List of Supported Operating System Versions

•GNU/Linux

Platform	Supported GNU/Linux versions
x86_64	•ALT 8 SP •ALT Server 9, 10 •ALT Workstation 9, 10 •Astra Linux Common Edition (Orel) 2.12 •Astra Linux Special Edition 1.5 (with cumulative patch 20201201SE15), 1.6 (with cumulative patch 20200722SE16), 1.7, 1.8 •CentOS 7, 8 •Debian 9, 10, 11, 12 •Fedora 37, 38 •GosLinux IC6 •Red Hat Enterprise Linux 7, 8 •RED OS 7.2 MUROM, RED OS 7.3 MUROM, RED OS 8 •SUSE Linux Enterprise Server 12 SP3 •Ubuntu 18.04, 20.04, 22.04, 24.04
x86	•ALT 8 SP •ALT Workstation 9, 10 •CentOS 7 •Debian 10
ARM64	•ALT 8 SP •ALT Server 9, 10 •ALT Workstation 9, 10 •Astra Linux Special Edition (Novorossiysk) 4.7 •CentOS 7, 8 •Debian 11, 12 •Ubuntu 18.04
E2K	•ALT 8 SP •ALT Server 10 •ALT Workstation 10 •Astra Linux Special Edition (Leningrad) 8.1 (with cumulative patch 8.120200429SE81) •Elbrus-D MCST 1.4 •GS CS Elbrus 8.32 TVGI.00311-28
ppc64el	•CentOS 8 •Ubuntu 20.04

In ALT 8 SP, 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 our technical support.

•FreeBSD

Platform	Supported FreeBSD versions
x86	11, 12, 13
x86_64	11, 12, 13

Dr.Web for UNIX File Servers can be installed on FreeBSD only from the universal package.

The correct operation of Dr.Web for UNIX File Servers on FreeBSD 13 requires that the compat12x Support Pack is installed.

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 from the command line, it is recommended to enable command auto-completion in your command shell (if disabled).

If you encounter any issue with installation of additional packages and components, refer to the documentation of your operating system version.

Disclaimer

•SpIDer Guard cannot use kernel modules (LKM) on operating systems started in the Xen hypervisor environment. An attempt to load the SpIDer Guard kernel module with the OS operating in the Xen environment can lead to a critical error of the OS kernel (so called “Kernel panic” error).

•The LKM is not supported for ARM64, E2K and IBM POWER (ppc64el) 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 the OS kernel is built with the enabled CONFIG_FANOTIFY_ACCESS_PERMISSIONS option.

Supported File Servers

1.Samba File Service

For integration with the Samba file service, the installed and configured Samba file server of versions 3.6–4.19 is required.

The SpIDer Guard for SMB monitor of Dr.Web for UNIX File Servers uses a specialized VFS SMB module to integrate into Samba. Several versions of the VFS SMB module built for different versions of Samba are supplied with the SpIDer Guard for SMB component; however, they may be incompatible with the version of Samba installed on your file server, 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 (with the CLUSTER_SUPPORT option if necessary).

The procedure of building the VFS SMB module from source code is described in the Building the VFS SMB Module section.

2.NSS File Service

For integration with the Novell Storage Services (NSS) file service, Novell Open Enterprise Server SP2 based on the SUSE Linux Enterprise Server 10 SP3 operating system or later (11 SP1, SP2) is required.

Compatibility with Security Subsystems

By default, Dr.Web for UNIX File Servers does not support the SELinux security subsystem. Moreover, Dr.Web for UNIX File Servers operates by default in a reduced functionality mode on the GNU/Linux systems that use mandatory access models (for example, on the systems distributed with the PARSEC mandatory access subsystem, which assigns different privilege levels, so-called mandatory levels, to users and files).

In case of installing Dr.Web for UNIX File Servers on systems with SELinux (as well as on systems that use mandatory access models), it is necessary to additionally configure the security subsystem, so that Dr.Web for UNIX File Servers would operate in a full functionality mode. For details, refer to the Configuring Security Subsystems section.