The initial signed audit log generated right after enabling signed audit failed verification.
Steps to reproduce: 1. Install regular CA. 2. Enable signing audit by setting log.instance.SignedAudit.logSigning=true in /etc/pki/pki-tomcat/ca/CS.cfg. 3. Restart CA. 4. Run "pki-server ca-audit-file-verify" which will run AuditVerify tool for all CA audit logs.
Actual result:
The signed audit log verification failed with the following output:
====== File: /var/lib/pki/pki-tomcat/logs/ca/signedAudit/ca_audit ====== Line 11: VERIFICATION FAILED: signature of /var/lib/pki/pki-tomcat/logs/ca/signedAudit/ca_audit:1 to /var/lib/pki/pki-tomcat/logs/ca/signedAudit/ca_audit:10 Verification process complete. Valid signatures: 3 Invalid signatures: 1
Expected result:
The signed audit log should pass verification in all cases, including immediately after enabling signed audit for the first time. If that's not the case the behavior should be documented properly.
See also ticket #2561 about verification failure due to log rotation.
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 ''
Metadata Update from @mharmsen: - Issue priority set to: --- - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @mharmsen: - Issue priority set to: critical (was: ---) - Issue set to the milestone: 10.4 (was: 0.0 NEEDS_TRIAGE)
Metadata Update from @edewata: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1404794
Metadata Update from @edewata: - Issue assigned to edewata
Fixed in master: * https://github.com/dogtagpki/pki/commit/ab2e24b3087368a2aadfcda77323a7d0aa70db80
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue set to the milestone: 10.4.8 (was: 10.4) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.4.9 (was: 10.4.8)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.4.9)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5.0 (was: 10.5)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.5.0-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/2754
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.
Login to comment on this ticket.