File Permissions and Privileges

To scan objects of the file system and neutralize threats, Dr.Web for Linux (or rather the user under whom it runs) requires the following permissions:

Action

Required rights

Listing all detected threats

Unrestricted. No special permission required.

Output of container contents (an archive, email file, and so on)

(display only corrupted or malicious elements)

Unrestricted. No special permission required.

Moving to quarantine

Unrestricted. The user can quarantine all infected files regardless of read or write permissions on them.

Deleting threats

The user needs to have write permissions for the file that is being deleted.

If the threat is detected in a file inside a container (an archive, an email message, and so on), the container is quarantined and not deleted.

Curing

Unrestricted. The access permissions and owner of a cured file remain the same after curing.

The file can be removed if deletion can cure the detected threat.

Restoring a file from quarantine

The user should have permissions to read the file and to write to the restore directory.

Deleting a file from quarantine

The user must possess write permissions to the file that was moved to quarantine.

To temporarily elevate permissions of Dr.Web for Linux running in graphical mode, you can use the corresponding button in Dr.Web for Linux window (which is available and displayed only if the privileges must be elevated to complete an operation successfully). To start Dr.Web for Linux in graphical mode or the command-line management tool with superuser privileges, you can use the su command to change the user or the sudo command to run a command as another user.