Kaspersky Industrial CyberSecurity for Linux Nodes

Updating the application from the command line

February 8, 2024

ID 221294

Follow the procedure below to locally update the previous version of the application to Kaspersky Industrial CyberSecurity for Linux Nodes 1.3.

The following steps are required to update the application:

  1. Run the Kaspersky Industrial CyberSecurity for Linux Nodes 1.3 installation package based on the type of the package manager.

    If you have a graphical user interface installed, then you also need to install the package containing the files of the graphical user interface.

  2. Acceptance of the terms of the End User License Agreement.

    If the terms of the End User License Agreement changed in the new version of the application, you need to accept the new terms of the End User License Agreement. Read the new version of the License Agreement located in the ~/.kics/<application version>/license.<language ID> directory. If you do not agree to the terms of the End User License Agreement, the application will not be updated.

  3. Acceptance of the terms of the Privacy Policy.

    If the terms of the Privacy Policy changed in the new version of the application, you need to accept the new terms of the Privacy Policy. Read the new version of the Privacy Policy located in the ~/.kics/<application version>/license.<language ID> directory. If you do not agree to the terms of the Privacy Policy, the application will not be updated.

  4. Acceptance of the Kaspersky Security Network Statement.

    If the terms of the Kaspersky Security Network Statement changed in the new version of the application, you need to accept or decline the new terms for participating in Kaspersky Security Network. Read the new version of the document located in the ~/.kics/<application version>/ksn_license.<language ID> directory. Refusing to participate in Kaspersky Security Network does not terminate Kaspersky Industrial CyberSecurity for Linux Nodes update process. You can enable, disable, or change Kaspersky Security Network mode later.

    If you participated in KSN and accepted the conditions of the Kaspersky Security Network Statement in a previous version of the application, you need to accept the conditions of the Kaspersky Security Network Statement when updating the application. Otherwise, use of KSN is disabled.

  5. Restarting the application.

If the terms of the End User License Agreement, Privacy Policy, or Kaspersky Security Network Statement have changed in the new version of the application, the application update will end with an error. In this case, you need to read the new version of the document and confirm that you have fully read and accepted its conditions. To do this, use the KICS_EULA_AGREED=yes, KICS_PRIVACY_POLICY_AGREED=yes and KICS_USE_KSN=yes/no environment variables.

To update the application:

  1. Execute the following command depending on the package manager. If you have a graphical user interface installed, then you also need to start the package containing the files of the graphical user interface.
    • for an RPM package.

      # [KICS_EULA_AGREED=yes] [KICS_PRIVACY_POLICY_AGREED=yes] [KICS_USE_KSN=yes/no] rpm -U --replacefiles --replacepkgs kics-1.3.0-<build number>.i386.rpm [kics-gui-1.3.0-<build number>.i386.rpm] (for 32-bit operating systems);

      # [KICS_EULA_AGREED=yes] [KICS_PRIVACY_POLICY_AGREED=yes] [KICS_USE_KSN=yes/no] rpm -U --replacefiles --replacepkgs kics-1.3.0-<build number>.x86_64.rpm [kics-gui-1.3.0-<build number>.x86_64.rpm] (for 64-bit operating systems);

    • for a DEB package:

      # [KICS_EULA_AGREED=yes] [KICS_PRIVACY_POLICY_AGREED=yes] [KICS_USE_KSN=yes/no] apt-get install ./kics_1.3.0-<build number>_i386.deb [./kics-gui_1.3.0-<build number>_i386.deb] (for 32-bit operating systems);

      # [KICS_EULA_AGREED=yes] [KICS_PRIVACY_POLICY_AGREED=yes] [KICS_USE_KSN=yes/no] apt-get install ./kics_1.3.0-<build number>_amd64.deb [./kics-gui_1.3.0-<build number>_amd64.deb] (for 64-bit operating systems).

  2. Restart the application.

If an error occurs while updating the application, the update is rolled back and the previous version of the application is started. In this case, an error message will be displayed, but the package manager (rpm/dpkg) will indicate the new version.

Did you find this article helpful?
What can we do better?
Thank you for your feedback! You're helping us improve.
Thank you for your feedback! You're helping us improve.