Open pki-bot opened 4 years ago
Comment from mharmsen (@mharmsen) at 2016-04-21 00:13:08
Per CS Bug/Ticket Triage held 04/19/2016: 10.4
Comment from roysjosh@gmail.com (@roysjosh) at 2017-02-27 14:02:51
Metadata Update from @roysjosh:
Comment from mharmsen (@mharmsen) at 2017-08-30 22:59:47
Metadata Update from @mharmsen:
Comment from mharmsen (@mharmsen) at 2017-10-25 17:55:43
[20171025] - Offline Triage ==> 10.6
Comment from mharmsen (@mharmsen) at 2017-10-25 17:55:43
Metadata Update from @mharmsen:
Comment from mharmsen (@mharmsen) at 2018-04-16 19:43:56
Per 10.5.x/10.6 Triage: 10.5
cfu needs to verify if this has already been fixed
Comment from mharmsen (@mharmsen) at 2018-04-16 19:43:57
Metadata Update from @mharmsen:
Comment from mharmsen (@mharmsen) at 2018-04-16 19:44:17
Metadata Update from @mharmsen:
Comment from mharmsen (@mharmsen) at 2018-04-16 19:45:29
Metadata Update from @mharmsen:
Comment from mharmsen (@mharmsen) at 2018-04-26 20:12:01
Per 10.5.x/10.6 Triage: 10.5
This issue was migrated from Pagure Issue #2284. Originally filed by roysjosh@gmail.com (@roysjosh) on 2016-04-16 00:16:26:
In attempting to integrate a custom CMC PKCS10/CRMF application with a production Dogtag PKI system, a disparity between Dogtag and the RFCs was noticed in the CRMF request handling.
A quick look through git didn't show many changes in the CMC/CRMF request handling so the issue likely still applies to git HEAD.
How reproducible:
Actual results:
Expected results: