dogtagpki

#2729 Fix new code In keywrap mode such that key recovery on KRA with HSM does not cause KRA to crash
Closed: duplicate Opened by mharmsen.

Closed: duplicate
Reopen Issue

This is a follow-on to https://pagure.io/dogtagpki/issue/2728 in which a work-around was installed to process the legacy code by default. This bug seeks to correct the new code such that it can be used as the new default.

Originally, because the AES KEY_WRAP algorithm was not suported by the HSM, we
needed to put the KRA in encrypt mode.

Recent code has allowed us to specify the AES-CBC-128 mode for key wrapping
algorithm, and to allow the KRA to be in key wrap mode. However, in this
mode, when a key recovery is attempted,
the KRA crashes due to a null pointer derefernece in the HSM (on a FIPS
machine(.

--- Additional comment from Red Hat Bugzilla Rules Engine on 2017-06-08
17:22:15 EDT ---

Since this bug report was entered in Red Hat Bugzilla, the release flag has
been set to ? to ensure that it is properly evaluated for this release.
```

Metadata Update from @mharmsen:
- Custom field cc adjusted to vakwetu@redhat.com,jmagne@redhat.com
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to Community
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1460029
- Custom field type adjusted to defect
- Custom field version adjusted to ''
- Issue assigned to ftweedal

Metadata Update from @mharmsen:
- Issue priority set to: critical

Per TRIAGE discussions, moving to 10.5

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.4)

Closed as duplicate of https://pagure.io/dogtagpki/issue/2728

Metadata Update from @mharmsen:
- Issue close_status updated to: duplicate
- Issue status updated to: Closed (was: Open)

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.0 (was: 10.5)

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.0-1.fc27

Metadata Update from @mharmsen:
- Custom field fixedinversion reset (from pki-core-10.5.0-1.fc27)

Metadata Update from @mharmsen:
- Assignee reset

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/2849

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.
Metadata
None
None
None
None
Low
defect
General
''
vakwetu@redhat.com,jmagne@redhat.com
''
Community
''
''
''
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.