Contents
Managing the application from the command line
You can manage the Kaspersky application from the command line.
Managing the unpacker from the command line
The unpacker of the Kaspersky application supports the following commands.
Command line options
Command |
Description |
---|---|
|
Display unpacker command help. This does not start the application.
|
|
Check the integrity of the
|
|
Allow the application to be run by an ordinary user.
|
|
Specify a directory for unpacking temporary files. The directory must not exist. If you specified the directory for unpacking temporary files manually, the application does not delete the directory after the application is closed. You must delete the temporary directory manually.
By default, the application places its files in the |
|
Do not run the application after unpacking.
|
|
Hide the unpacking indicator (quiet unpacking mode).
|
Managing the application from the command line
The Kaspersky application supports the following management commands.
Command line options
Command |
Description |
---|---|
|
Display command line syntax help.
|
|
Enable trace collection.
|
|
Set trace level.
|
|
Specify the directory for saving application files (reports, traces, quarantine, etc).
By default, the application saves files in the following directory:
|
|
Automatically accept the End User License Agreement, the Privacy Policy, and the KSN Statement.
|
|
Disable the encryption of traces, dumps, and reports.
|
|
Add all mount points except service and network mount points to the scan scope. By default, the application scans system memory, startup objects, and boot sectors of the computer.
|
|
Run a scan of only the defined scope (custom folder scan). With this option, the application excludes the system memory, startup objects, and boot sectors of the computer from scanning. To run a custom folder scan, define a scan scope using the
|
|
Add a directory to the scan scope. You can add multiple directories. The application supports full paths. By default, the application scans system memory, startup objects, and boot sectors of the computer.
|
|
Add multiple directories, listed in a text file, to the scan scope. Do not enclose paths in the file in quotation marks. Each path must start on a new line. The encoding of the file must be ANSI or UTF8 with BOM. By default, the application scans system memory, startup objects, and boot sectors of the computer.
|
|
Exclude a directory or file from the scan scope. You can exclude multiple objects. The application supports full paths. By default, the application scans system memory, startup objects, and boot sectors of the computer.
|
|
Exclude multiple directories or files, listed in a text file, from scanning. Do not enclose paths in the file in quotation marks. Each path must start on a new line. The encoding of the file must be ANSI or UTF8 with BOM. By default, the application scans system memory, startup objects, and boot sectors of the computer.
|
|
Enable the generation of detailed reports. The detailed report reflects all application events. By default, the application generates standard reports. A standard report includes warning and error events.
|
|
Connect to a proxy server with a configuration file. The application only supports absolute paths.
|
Examples of scan commands
1 Standard scan (system memory, startup objects, and boot sectors of the computer).
./kaspl.run
2 Scan the /home directory
./kaspl.run -- -customonly -custom /home
3 Scanning a list of directories from the scan_scope.txt file
./kaspl.run -- -customonly -customlist /tmp/folder/scan_scope.txt
4 Standard scan excluding the /media directory
./kaspl.run -- -exclude /media
Requirements for the proxy server configuration file
The Kaspersky application can automatically determine proxy server connection settings. If the application cannot connect to the proxy server automatically, you can specify connection settings using a configuration file. To do so, you must run the application on the command line with the -proxyconfig <file_path>
option.
Configuration file requirements:
- File name —
proxy.dat
- Encoding — UTF8 without BOM
Syntax:
server=<proxy_server_address>
#For example, server=myproxy.com
port=<port>
#For example, port=1122
username=<user_name>
#For example, username=Fred
password=<password>
#For example, password=1234