dogtagpki

#1166 Recovery procedure for corrupted CS.cfg
Closed: Fixed Opened by edewata.

Closed: Fixed
Reopen Issue

There should be a documented procedure (or automated tool) to recover corrupted CS.cfg. This may involve:

  • providing a sample of a fully configured CS.cfg (not CS.cfg.in)
  • obtaining certificates, certificate requests, modulus, etc. from NSS database
  • replacing the hostname and base DN

This procedure is needed for all Dogtag since version 9.

The parameters that need to be recovered include (but not limited to):

  • ca.*.cert
  • ca.*.certreq
  • cloning.*.privkey.id
  • cloning.*.pubkey.exponent
  • cloning.*.pubkey.modulus

http://pki.fedoraproject.org/wiki/Recovery

Per CS/DS Meeting of 09/29/2014: Milestone 10.3

The above link provides the recovery procedure for Dogtag 9.0 master CA. Other improvements will be done in ticket #1186.

Metadata Update from @edewata:
- Issue set to the milestone: 10.2.1

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/1729

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.
Metadata
None
None
None
None
Normal
defect
General
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.