System Requirements and Compatibility |
In this section: •List of Supported Operating System Distributions. •Required Additional Components and Packages. •Compatibility with Components of Operating Systems. •Compatibility with Security Subsystems. You can use Dr.Web for Linux on a computer that meets the following requirements:
To ensure the correct operation of Dr.Web for Linux, open the following ports:
List of Supported Operating System Distributions
For other UNIX distributions that meet the abovementioned requirements full compatibility with Dr.Web for Linux is not guaranteed. If a compatibility issue occurs, contact technical support. Required Additional Components and Packages •To enable Dr.Web for Linux operation in graphical mode and startup of the program for installation and uninstallation in graphical 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). •To start the installer or uninstaller, designed for the command line, in graphical mode, a terminal emulator (such as xterm, xvt, and so on) 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 Dr.Web for Linux, PAM must be used in the operating system.
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 LKM module, which is supplied in pre-built form within the product. The Dr.Web for Linux distribution has LKM modules for all GNU/Linux systems mentioned above. If required, you can build a kernel module independently from the distributed source codes for any OS that uses the kernel GNU/Linux of version 2.6.x and later.
•SpIDer Gate may conflict 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 of SpIDer Gate 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, the 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 your 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 NetFilter, and looks like as follows: after disabling SpIDer Gate, the network connections are broken and cannot be re-established. If you face this problem, it is recommended that you upgrade your OS to a version that includes NetFilter 1.4.15 or above. The ways to resolve the problem are described in the section “Description of 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). To install Dr.Web for Linux on systems with SELinux (as well as systems that use mandatory access control models), you may require to configure a security subsystem, so that Dr.Web for Linux operates in full functionality mode. For details, refer to the section Configuring Security Subsystems. |