Minor updates

Under “minor updates” we consider incremental feature updates (where the version number jumps from X.1.0 to X.2.0) and patch updates (where the version number jumps from X.X.0 to X.X.1). We encourage everyone to always update to the latest minor version, but keeping up with patch updates is even more important as these entail security and (grave) bug fixes.

Patch updates are always as minimal as possible and have extremely low chances of breaking your installation. Please apply them as soon as possible. We encourage all customers with a support contract to contact CipherMail (or their support partner) when they encounter issues with the update procedure.

Note

Online updating the CipherMail application is only supported on the professional version and requires a valid license Pro/Ent only. Users of the Community Gateway should follow the instructions for Community Edition updates.

Pro/Ent only The professional edition will periodically send an email to the registered root user if updates are available. If updates are available, the ‘updates’ line in the administrative status page will show that updates are available.

Updates should be installed using the console tool:

  1. Log in with SSH or directly on the (VMware, HyperV, cloud) console.

  2. From the CipherMail console application, click Other, then select Update from the pull-down menu.

    Note

    Alternatively updates can be installed from the command line using the dnf command:

    sudo dnf update

  3. Confirm the update.

  4. Updates will now be downloaded and applied. If CipherMail application updates were installed, an Ansible playbook will automatically kick off to configure the application.

  5. We highly recommend rebooting the system soon after you update it. This may not be strictly required in all cases, but it makes sure that all running services have loaded their new environments.

Warning

For HA cluster administrators: always update packages on one HA cluster node at a time. Delay updating the other node(s) until the node that was updated is back online and that the cluster status reports that all three nodes are active again.