System Requirements

Top  Previous  Next

You can use Dr.Web for Linux on a computer that meets the following requirements:

Component

Requirement

Platform

CPU with the Intel/AMD architecture and command system are supported: 32-bit (IA-32, x86); 64-bit (x86-64, x64, amd64).

Space on
hard disk

At least 512 MB of free disk space on a volume where the Dr.Web for Linux directories are located.

Operating
system

Linux for Intel x86/amd64 platform based on kernel ver. 2.6.37 or later, and using PAM and library glibc ver. 2.13 or later.

Tested Linux distributions are listed below.

For systems operating on 64-bit platforms, support of 32-bit applications must be enabled (probably, additional libraries must be installed for this, see below).

 

For the correct operation of SpIDer Gate, OS kernel must be built with inclusion of the following options:

CONFIG_NETLINK_DIAG, CONFIG_INET_TCP_DIAG;

CONFIG_NF_CONNTRACK_IPV4, CONFIG_NF_CONNTRACK_IPV6,
CONFIG_NF_CONNTRACK_EVENTS;

CONFIG_NETFILTER_NETLINK_QUEUE,
CONFIG_NETFILTER_NETLINK_QUEUE_CT, CONFIG_NETFILTER_XT_MARK.

The set of required options from the specified list can depend on the used distribution kit of GNU/Linux.

Other

The following valid network connections:

An Internet connection to download updates and for sending requests to the Dr.Web Cloud service (only if it is manually authorized by the user).

When operating in central protection mode, connection to the server on the local network is enough; connection to the Internet is not required.

Dr.Web for Linux is incompatible with other anti-virus software programs. To avoid system errors and data loss that may occur when installing two anti-viruses on one computer, remove all other anti-virus programs from the computer before the Dr.Web for Linux installation.

The product was tested on the followingLinux distributions (32-bit and 64-bit):

Linux distribution name
Linux

Versions

Required additional libraries for support of 32-bit applications for the 64-bit OS version

Debian

8.0 – 8.6, 9.0

libc6-i386

Fedora

24, 25

glibc.i686

Mint

18

libc6-i386

Ubuntu

14.04, 16.04, 16.10, 17.04

libc6-i386

CentOS

6.6, 6.7, 7.1, 7.2, 7.3

glibc.i686

Red Hat Enterprise Linux

6.6, 6.7, 7.1, 7.2, 7.3

glibc.i686

SUSE Linux Enterprise Server

11 SP3, 11 SP4, 12

Other Linux distributions that meet the above-mentioned requirements have not been tested for compatibility with Dr.Web for Linux but may be supported. If a compatibility issue occurs, contact technical support on the official website at http://support.drweb.com/request/.

Required additional components and packages

To enable Dr.Web for Linux operation in graphical mode and startup of the program for product installation and removal in graphic mode, X Window System graphic shell and any window manager is required. Moreover, for correct operation of the indicator for Ubuntu Unity desktop environment, the additional library may be required (by default, the library named libappindicator1 is required).

For scheduled scanning, crond must be installed in the operating system.

To start the product installer or uninstaller, designed for the command line, in graphic mode, a terminal emulator (such as xterm, xvt, etc.) is required.

To enable privileges elevation during installation or uninstallation, one of the following utilities is required: su, sudo, gksu, gksudo, kdesu, kdesudo. For correct operation of the product, PAM must be used in the operating system.

For convenient work with Dr.Web for Linux in the command line, you can enable command auto-completion in the used command shell (if disabled).

Compatibility with components of operating systems

By default, SpIDer Guard uses the fanotify system mechanism, while on those operating systems on which the fanotify is not implemented or is unavailable for other reasons, the component uses a special loadable kernel module, which is supplied in pre-built form within the product. The product distribution has kernel modules for all GNU/Linux systems mentioned above. If required, you can build a kernel module independently from the distributed sorce codes for any OS that uses the kernel GNU/Linux of version 2.6.x and later.

SpIDer Gate may conflict with other with other firewalls installed in your system:

Conflict with Shorewall and SuseFirewall2 (for SUSE Linux Enterprise Server). In case of conflict with these firewalls, an error message with a code x109 is displayed. A way to resolve this conflict is described in the Appendix "Known Errors".

Conflict with FirewallD (for Fedora, CentOS, Red Hat Enterprise Linux). In case of conflict with these firewall, a SpIDer Gate error message with a code x102 is displayed. A way to resolve this conflict is described in the Appendix "Known Errors".

In case if the used OS includes the version of NetFilter less than 1.4.15, SpIDer Gate may operate incorrectly. This problem is related to the internal error of the NetFilter, and looks like as follows: after disabling SpIDer Gate, the network connections are broken and cannot be re-established. If you run into this problem, it is recommended to upgrade your OS to version that includes NetFilter 1.4.15 or above. How to resolve the problem, is described in the Appendix "Known Errors".

Under normal operation, SpIDer Gate is compatible with all user applications that use network, including web browsers and mail clients. For the correct scanning of secured connections, it is necessary to add the certificate Dr.Web for Linux to the list of trusted certificates of those applications that use the secured connections (for example, web browsers and mail clients).

After changing operation of SpIDer Gate (enabling of the previously disabled monitor, change of the scanning mode of secured connections), it is necessary to restart mail clients that use the IMAP protocol to receive email messages from the mail server.

Compatibility with security subsystems

By default, Dr.Web for Linux does not support SELinux. In addition, Dr.Web for Linux 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 Linux is required for systems with SELinux, as well as for systems that use mandatory access models, it is necessary to execute additional settings of security subsystems so that Dr.Web for Linux operates in full functionality mode. For details, refer to the section Configuring Security Systems.

If you encounter any problem with installation of additional packages and components, refer to manuals for the used distribution of the operating system.