We are missing man pages for the following tools: CMCRequest, CMCRevoke, CMCSharedToken, and CMCResponse.
In addition, the existing tool CMCEnroll has not been updated to support the latest CMC feature update, and yet its man page exists. Should probably add a note in there to state the fact.
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1545388 - Custom field type adjusted to None - Custom field version adjusted to None
Author: Christina Fu cfu@redhat.com Date: Mon Feb 26 13:16:01 2018 -0800
Ticket #2940 [MAN] Missing Man pages for tools CMCRequest, CMCResponse, CMCSharedToken, and CMCRevoke This patch adds man pages for CMCRequest, CMCResponse, and CMCSharedToken. In addition, the usage in CMCResponse has been enhanced to include a verbose mode which will output certs in Base64 encoding individually. A "note" has been added to CMCRevoke --help to direct users to CMCRequest for better usability. The man page for CMCRevoke is intentionaly left out for this reason. The URL in CMCRequest.1 is a placeholder for the follow-up patch. It will be replaced once the examples are complete. This patch addresses https://pagure.io/dogtagpki/issue/2940 Change-Id: Id1df31a29207a0d12d50b7a3b959a3abcd9748d0
Metadata Update from @cfu: - Issue assigned to cfu - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5.7 (was: 10.5)
spec file patch: https://review.gerrithub.io/#/c/404194/
pushed to master: commit 827fe40c8064bcb779c52c666f09a1e162c61648 (HEAD -> master, origin/master, origin/HEAD) Author: Christina Fu cfu@redhat.com Date: Fri Mar 16 13:43:04 2018 -0700
Ticket #2940 (spec file only) Change-Id: Ice17b4f985a7dc7c092902d920d40272c751941a
Metadata Update from @cfu: - Issue set to the milestone: 10.5 (was: 10.5.7)
commit 3ce3ae9bd73a906beb0254a7488b15e11ddcf905 Author: Christina Fu cfu@redhat.com Date: Mon Mar 26 10:09:42 2018 -0700
reflect dogtagpki url change in CMCRequest man page. Change-Id: I8eb5884a26850b87f378c4417939c873c27fd409
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.5.7-2.fc27
commit 2e299050016094c4ab9b739bc68a27787d8aadb4 (HEAD -> master, origin/master, origin/HEAD) Author: Christina Fu cfu@redhat.com Date: Mon Apr 16 14:28:39 2018 -0700
Ticket #2940 post-ticket simple typo fix. Change-Id: I98558f607cb611981bcafd42d6500fd26a9664be
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5.8 (was: 10.5.7)
Per 10.5.x/10.6 Triage: 10.5
Metadata Update from @mharmsen: - Issue priority set to: critical (was: major)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.5.8-1.fc27 (was: pki-core-10.5.7-2.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/3058
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.