A minor typo in CRMFPopClient tool.
Steps to Reproduce:
See the last statement in the CRMFPopClient response that has typo 'requrest'. 1.# CRMFPopClient -d /opt/rhqa_pki/admin_certs_db -p SECret.123 -n "cn=FooUser123, uid=FooUser123" -q POP_SUCCESS -b /opt/rhqa_pki/kra_transport.txt -y -v -o /opt/rhqa_pki/certs_db/crmf.req Initializing security database: /opt/rhqa_pki/admin_certs_db Loading transport certificate Parsing subject DN RDN: UID=FooUser123 RDN: CN=FooUser123 Generating key pair Keypair private key id: -3e707cb45b34eb8cb06549771f4b2e54beeaa238 Using key wrap algorithm: AES KeyWrap/Padding Creating certificate request CRMFPopClient: self_sign true. Generating SubjectKeyIdentifier extension. CryptoUtil: createKeyIdentifier: begins Creating signer Creating POP Creating CRMF request Storing CRMF requrest into /opt/rhqa_pki/certs_db/crmf.req
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=1524729 - Custom field type adjusted to None - Custom field version adjusted to None
Fixed in master branch:
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue set to the milestone: 10.6.0 (was: 10.6) - Issue status updated to: Closed (was: Open)
Per 10.5.x/10.6 Triage: 10.6
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/2994
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.