while fixing Bug 671522 - TPSAuditVerify fails, I found both the servers (JAVA and TPS) and the tool (AuditVerify) do not currently have code to support signing Audit log with EC keys.
Per PKI Bug Council of 11/29/2016: 10.4 - critical
Metadata Update from @cfu: - Issue set to the milestone: 10.4
Per email from dsirrine on 04/10/2017: moving to 10.5
Metadata Update from @mharmsen: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue set to the milestone: 10.5 (was: 10.4)
Metadata Update from @mharmsen: - Issue priority set to: major (was: critical)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Per 10.5.x/10.6 Triage: 10.5
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.6)
Metadata Update from @mharmsen: - Issue assigned to cfu - Issue priority set to: blocker (was: major)
https://review.gerrithub.io/c/dogtagpki/pki/+/421945
Christina Fu 2018-08-10 21:54:49 EDT
commit 9c4788ad6fb28f42e99776216969a63c3d13eb40 (HEAD -> master, origin/master, origin/HEAD, ticket-2481-eccAuditVerify-master) Author: Christina Fu cfu@cfu-fedora.usersys.redhat.com Date: Fri Aug 10 15:40:19 2018 -0700
Ticket #2481 ECC keys not supported for signing audit logs This patch adds support for ECC audit log signing key. All enrollment profiles for audit signing certificate are updated to allow that. fixes https://pagure.io/dogtagpki/issue/2481 Change-Id: I3785365b152690f57c3904c15dfa7b2999048930
Metadata Update from @mharmsen: - Issue close_status updated to: fixed - Issue set to the milestone: 10.5.12 (was: 10.5) - Issue status updated to: Closed (was: Open)
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/2601
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.