Installation manual

20
5.1. User Specic Conguration
User Specic Conguration mechanism is implemented in the product in order to provide user with enhanced
conguration functionality. It allows to dene NOD32 anti-virus scanner parameters selectively for user accessing le
system objects.
Please note that the detailed description of this functionality can be found in nod32.cfg(5) manual page and
manual pages referenced there. Thus in this section we will only provide short example of user specic conguration
denition.
Let’s say we use nod32dac module for the scanning purpose. This module is subjected to the conguration section
[dac] found within main NOD32 conguration le. The example of the section can be as follows.
[dac]
agent_enabled = yes
event_mask = 5
ctl_incl = “/home“
action_on_processed = accept
In order to provide individual parameters setting one has to dene ‘user_cong‘ parameter with the path to the
special conguration le where the individual setting will be stored. In the next example we create reference to the
special conguration le ’nod32dac_spec.cfg’ located within default conguration le directory.
[dac]
agent_enabled = yes
event_mask = 5
ctl_incl = “/home“
action_on_processed = accept
user_cong = “nod32smtp_spec.cfg“
Note that the ‘user_cong‘ parameter accepts also absolute path to the specic conguration le.
Once special conguration le referenced from within [dac] section we have to create this le and provide the le
with an appropriate individual settings.
In the next example we create individual parameter setting of parameter ’action_on_processed’ for user
’username’.
[username]
action_on_processed = reject
Note that the section header name of the special section contains identication of the user for which we have created
the individual setting. The section body then contains individual parameters specied for this identication. Thus with
this special conguration all users attempting to access le-system will be processed, i.e. all le system objects accessed
by the users will be scanned for inltrations, with exception to the user ’username’ that will be rejected, i.e. the access
of the le system will be blocked for this user.
5.2. Handle Object Policy
The Handle Object Policy (see gure 5-1) is a mechanism that provides handling of the scanned objects depending
on their scanning status. The mechanism is based on so-called action conguration options (’action_on_processed’,
’action_on_infected’, ’action_on_uncleanable’, ’action_on_notscanned’) combined with Anti-Virus enabling
NOD32 for Linux/BSD File Server