After the initial setup, the application creates the following configuration files:
The agreements.ini configuration file contains settings related to the License Agreement, Privacy Policy, and Kaspersky Security Network Statement.
The kesl.ini configuration file contains the settings described in the following table.
If necessary, you can edit the values of the settings in these files.
The default values in these files should be changed only under the supervision of Technical Support specialists and in accordance with their instructions.
Settings of the kesl.ini configuration file
Setting |
Description |
Values |
|---|---|---|
The [General] section contains the following settings: |
||
|
A unique installation identifier. |
Filled out automatically during the initial setup of the application. |
|
The number of environment variables that the application captures from the command call. |
Default value: 50. |
|
The locale used for the application events sent to Kaspersky Security Center. |
The locale in the format specified by RFC 3066. If the The locale of the graphical interface and the application command line depends on the value of the |
|
Limit on the application's use of memory in megabytes. |
Default value: 8192. |
|
Number of arguments that the application captures from the exec call. |
Default value: 50. |
|
The user's unique device ID. |
Filled out automatically during the initial setup of the application. |
|
Enables generation of trace files at application startup. |
|
|
Enables the creation of a dump file when application failure occurs. |
|
|
Indicates use of fanotify notifications. |
Filled out automatically during the initial setup of the application. |
|
Path to a socket for a remote connection to, say, a graphical interface and the kesl-control utility. |
Default value: /var/run/bl4control. |
|
Format of the installed application package. |
Filled out automatically during the initial setup of the application. |
|
Indicates use of a public DNS. |
If there are errors accessing servers through the system DNS, the application uses a public DNS. This is needed for updating application databases and maintaining device security. The application will use the following public DNSes in this order:
The application's requests may contain domain addresses and the user's external IP address, since the application establishes a TCP/UDP connection with the DNS server. This information is necessary, for example, to check the certificate of a web resource when interacting via HTTPS. If the application is using a public DNS server, data processing rules are governed by the Privacy Policy of the corresponding service. If you need to block the application from using a public DNS server, contact Technical Support for a private patch. |
The [Network] section contains the following settings: |
||
|
A mark in the iptables rules for forwarding traffic to the application for processing by Web Threat Protection tasks. You may need to change this mark if a device with the application runs other software that uses the ninth bit of the TCP packet mask, and a conflict occurs. |
A decimal value or hexadecimal number with the prefix 0x. Default value: 0x100. |
|
A mark in the iptables rules for forwarding traffic to the application for processing by Network Threat Protection tasks. You may need to change this mark if a device with the application runs other software that uses the ninth bit of the TCP packet mask, and a conflict occurs. |
A decimal value or hexadecimal number with the prefix 0x. Default value: 0x200. |
|
A mark used to indicate packets created or scanned by the application, so that the application does not scan them again. |
A decimal value or hexadecimal number with the prefix 0x. Default value: 0x400. |
|
A mark used to indicate packages created or scanned by the application to prevent them from being logged by the iptable utility. |
A decimal value or hexadecimal number with the prefix 0x. Default value: 0x800. |
|
Number of the routing table. |
Default value: 101. |
The [Watchdog] section contains the following settings: |
||
|
Maximum time to wait for the controlled process to complete from the moment the Watchdog server sends the HEADSHOT signal to the controlled process. |
Default value: 2 minutes.
|
|
Maximum time interval from the moment the REGISTER message is received to the moment the SUCCESSFUL_STARTUP message is received. |
Default value: 3 minutes. |
|
Maximum time to wait for the controlled process to complete from the moment the Watchdog server sends the SIGKILL signal to the controlled process. If the controlled process does not finish before this time elapses, the action specified by the --failed-kill setting is performed. |
Default value: 2 days. |
|
The interval with which the application attempts to send a PONG message to a server in response to a received PING message. |
Default value: 2000 ms. |
|
Maximum number of consecutive unsuccessful attempts to start the application. |
Default value: 5. |
|
Maximum time interval during which the application should send a message to the Watchdog server. If a message is not received from the application within this time interval, the Watchdog server begins the procedure to terminate the controlled process. |
Default value: 2 minutes. |
|
Maximum time from the start of the controlled process to the moment when a connection with the Watchdog server is established by the application. If the application does not establish a connection in this time interval, the Watchdog server begins the procedure to terminate the controlled process. |
Default value: 3 minutes. |
|
Maximum time from the moment the application connects to the Watchdog server to the moment the server receives a REGISTER message. |
Default value: 500 ms. |
|
Maximum time to wait for the controlled process to complete from the moment the Watchdog server sends the SHUTDOWN signal to the controlled process. |
Default value: 2 minutes. |
|
Limit on the use of virtual memory by the controlled process. If the controlled process uses more virtual memory than this limit, the Watchdog server begins the procedure to terminate the controlled process. |
|
|
Limit on the size of the swap file of the controlled process. If the swap file of the controlled process exceeds this limit, the Watchdog server begins the procedure to terminate the controlled process. |
|
|
Limit on the resident set size for the controlled process. If the resident set size of the controlled process exceeds this limit, the Watchdog server begins the procedure to terminate the controlled process. |
Default value: |