A new framework might be needed to keep track security upgrades that will affect the system behavior. This framework is separate from the configuration upgrade framework (#554) and the database upgrade framework (#710) that should not affect the system behavior.
Security upgrades consist of a series of changes to the server settings or the contents of the database. The upgrades can be optional or mandatory. The upgrades generally can be run in any order in separate executions, but some upgrades might have dependencies on others. Each upgrade can be implemented as a script or a manual procedure. An administrator may decide to run the upgrade script, postpone the upgrade, ignore the upgrade, or perform the upgrade manually. The framework should keep track the status of each upgrade (e.g. new, in progress, completed, ignored). The server might not start if there are incomplete mandatory upgrades.
For example:
$ pki-security-upgrade Upgrade #14: Remove SHA1withRSA from caAdminCert profile. Type: Optional Status: New Run [Yes/No/Ignore/Manual]? Ignore This upgrade is ignored. Upgrade #26: Enable certificate revocation checking for authentication. Type: Mandatory Status: New Run [Yes/No/Ignore/Manual]? Yes This upgrade is complete.
Proposed milestone: 10.3
Proposed Milestone: 10.3 (per CS Meeting of 09/17/2014)
Metadata Update from @edewata: - Issue set to the milestone: UNTRIAGED
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1698
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.