In working for the NIST SP800-108 and GP key sanity check patches, some additional items were found with ComputeSessionKey error reporting and DiversifyKey mkmappings
attachment pki-common_processComputeSessionKey_fixedErrorReporting.patch
attachment pki-common_processDiversifyKey_fixedmkmappings.patch
pki-common_processComputeSessionKey_fixedErrorReporting.patch doesn't seem to apply cleanly. I swapped the order of the two patches but it didn't help.
proposed Milestone: 10.2.1 - Per Dogtag 10.2.3 meeting of 09/25/2014
pushed to master: commit 4c910296a6c6c8bf74fbdace740680db2f1fecab
pushed to DOGTAG_10_2_0_BRANCH commit cdc186f378b0afe526a35400785f47fc5559395c
(cherry picked from commit 4c910296a6c6c8bf74fbdace740680db2f1fecab)
pushed to DOGTAG_10_2_RHEL_BRANCH commit d3051dd3c992b62fc10607bb388121cba50a7003
make this ticket a patch-integration only bug. Ticket 865 (when TPS part is written) will be the actual feature ticket and tested fully.
Metadata Update from @klamb: - Issue assigned to cfu - Issue set to the milestone: 10.2.1
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/1433
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.