Supported Upgrade Paths
In Key Manager version numbering the first two numbers indicate the major release version, while the third number indicates which maintenance release the version is:
Major.major.maintenance
Key Manager can be upgraded from a major version to the next two major versions; for example from 5.1.x to 5.2.x, or 5.3.x .
Key Manager can also be upgraded from any maintenance release of the same major version to any newer maintenance release of the same major version; for example from 4.3.2 to 4.3.7
Table 8.1. Possible upgrade paths
| From version | Destination version |
|---|---|
| 4.3.0 | 5.0.0, 5.1.0 |
| 5.0.0 | 5.1.0, 5.2.0 |
| 5.1.0 | 5.2.0, 5.3.0 |
| 5.2.0 | 5.3.0, 6.0.0 |
| 5.3.0 | 6.0.0, 7.0.0 |
| 6.0.0 | 7.0.0 |
To upgrade from any earlier versions to version 7.0.0, you need to have first upgraded to one of the two previous major versions, as indicated by the previous upgrade path table. For instructions about upgrading to one of the previously-described versions, see their respective versions of the PrivX Key Manager Installation Manuals.
When planning Key Manager upgrade, the system requirements mentioned in chapter 3.2 of the PrivX Key Manager Product Description document need to be satisfied for any versions involved in the upgrade process. You should also review the release notes of the involved versions before the upgrade process.
Also ssh-mgr-host-utility shipped with the last minor Key Manager release can be used with the latest Key Manager version. Note that while the previous versions of ssh-mgr-host-utility may work with the newer versions of the Key Manager system, they typically do not support the Key Manager features that were introduced in the subsequent system versions.
Upgrading ssh-mgr-host-utility is not a mandatory part of upgrading the Key Manager system. However, new releases of Key Manager may introduce functionality that is not supported by the older versions of ssh-mgr-host-utility.