dogtagpki

#2654 Adding object IDs into signature generation audit events.
Closed: fixed Opened by edewata.

Closed: fixed
Reopen Issue

All events related to signature generation using a CA signing key should be modified to include the following information:

  • Name/identifier of object being signed
  • Identifier of key used for signing

This includes at least the following events:

  • certificate signing
  • OCSP signing
  • CRL signing

Metadata Update from @edewata:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to Community
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field type adjusted to defect
- Custom field version adjusted to ''
- Issue set to the milestone: 10.4

Metadata Update from @mharmsen:
- Issue priority set to: critical

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1404075, https://bugzilla.redhat.com/show_bug.cgi?id=1445532

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.4)

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

Per CS/DS Meeting 09/25/2017: 10.5 blocker

Metadata Update from @mharmsen:
- Issue priority set to: blocker (was: major)

Metadata Update from @edewata:
- Issue assigned to edewata

Cert signing:

  • https://github.com/dogtagpki/pki/blob/e16be807c2cca6d717dad550343b6aeff347d91b/base/ca/src/com/netscape/ca/CAService.java#L862

OCSP signing:

  • https://github.com/dogtagpki/pki/blob/e16be807c2cca6d717dad550343b6aeff347d91b/base/ca/src/com/netscape/ca/CertificateAuthority.java#L2437
  • https://github.com/dogtagpki/pki/blob/e16be807c2cca6d717dad550343b6aeff347d91b/base/server/cms/src/com/netscape/cms/ocsp/DefStore.java#L406
  • https://github.com/dogtagpki/pki/blob/e16be807c2cca6d717dad550343b6aeff347d91b/base/server/cms/src/com/netscape/cms/ocsp/LDAPStore.java#L353

CRL signing:

  • https://github.com/dogtagpki/pki/blob/e16be807c2cca6d717dad550343b6aeff347d91b/base/ca/src/com/netscape/ca/CRLIssuingPoint.java#L2777
  • https://github.com/dogtagpki/pki/blob/e16be807c2cca6d717dad550343b6aeff347d91b/base/ca/src/com/netscape/ca/CRLIssuingPoint.java#L2887
Edited by edewata

Per cfu's suggestion, instead of adding key ID into each signing event, the key ID will be logged at server startup time under the following audit events:

  • CERT_SIGNING_INFO
  • OCSP_SIGNING_INFO
  • CRL_SIGNING_INFO

Fixed in master:

  • https://github.com/dogtagpki/pki/commit/4551eb1ce6b14e4a37f9c70b3bfd6c9050e13f10

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.5.0 (was: 10.5)
- Issue status updated to: Closed (was: Open)

For LWCA see also ticket #2839.

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.1 (was: 10.5.0)

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.1-1.fc27

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

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
Lowest
defect
General
''
''
Community
''
''
''
pki-core-10.5.1-1.fc27
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.