ESET GATEWAY SECURITY, Installation Manual

Page: 21 / 38

21
Infected template: esets_infected
Not scanned template: esets_not_scanned
After submitting the list of templates go to ‘Templates‘ page of the main ‘Config‘ menu. You
shall see a parameter ‘Path‘ that defines SafeSquid templates directory path (in the next we
assume the parameter is ‘/opt/safesquid/templates‘). Ensure that an appropriate directory exists
and if not, create it. To access the ESETS predefined templates from within this directory you
have to provide an appropriate links using the following shell statements:
ln -s @LIBDIR/ssfi/templates/ssfi_infected.html /opt/safesquid/ssfi_infected.html
ln -s @LIBDIR/ssfi/templates/ssfi_not_scanned.html /opt/safesquid/ssfi_not_scanned.html
You have also to add the new templates definitions in the SafeSquid configuration by
pressing ‘Add‘ in the ‘Templates‘ section. In the list that appears the following parameters have to
be defined for infected ESETS blocking page:
Comment: ESET Gateway Security infected template
Name: esets_infected
File: ssfi_infected.html
Mime type: text/html
Response code: 200
Type: File
Parsable: Yes
resp. for not-scanned ESETS blocking page the list is as follows:
Comment: ESET Gateway Security not scanned template
Name: esets_not_scanned
File: ssfi_not_scanned.html
Mime type: text/html
Response code: 200
Type: File
Parsable: Yes
For reread of newly created configuration, reload SafeSquid and also ESETS daemon.
chapter 5
Integration with Internet Gateway services