Managing Application Privileges

Top  Previous  Next

Some operations with Dr.Web Anti-virus for Linux can be performed in graphics mode only if the application has elevated privileges that correspond to the superuser permissions. Among such actions are the following:

1.Management of objects moved to the system Quarantine (that is, to the non-user Quarantine directory);
2.Check of files and directories of other users (in particular, of superuser);
3.Disable SpIDer Guard;
4.Removal of a license key file, connection and disconnection from the central protection server.

All pages that provide for actions requiring superuser privileges contain a special button with a lock icon. The icon indicates whether or not the application has superuser privileges:

lock_lock

– Application does not have superuser privileges.

Click the icon to elevate the privileges.

lock_unlock

– Application has superuser rights.

Click the icon to the lower privileges; that is, the application is running with the privileges of the user who started it.

On attempt to elevate privileges (i.e., once the lock icon is clicked) a pop-up menu that allows to select an elevation method appears.

lock_menu

Picture 26. Privilege elevation menu

The following two methods are available: using the su command (change the current user) and using the sudo command profile. Depending on the settings, a password dialog may appear after you select one of the methods. If so, enter the superuser password in the entry field. When lowering the privileges, password is not required.

warning

To enable privilege elevation, the su or sudo utilities and the xterm terminal emulator are required.

Instead of this, it is recommended to install one of the utilities for elevating privileges from the desktop environment: gksu, kdesu, beesu, gksudo, kdesudo, beesudo, or xterm.

If the application was started with superuser privileges, the icon of an open lock always displays unavailable. Thus, an option to lower the privileges is disabled.