#2777 Fix ca-authority-key-export server side code to support both AES and 3DES
Closed: migrated a year ago by dmoluguw. Opened 4 years ago by mharmsen.

The ca-authority-key-export command outputs a PKIArchiveOptions object wrapped
to the main CA public key (a hybrid encryption where a symmetric key is wrapped
to the public key, and the private key to be exported is enciphered with a symmetric
algorithm). The symmetric algorithm used must continue to be 3DES as it cannot be changed to AES at this time.

The corresponding decryption code in KeyRetrieverRunner must continue to support
decrypting 3DES-enciphered keys.

Metadata Update from @mharmsen:
- 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=1448235
- Custom field type adjusted to defect
- Custom field version adjusted to ''
- Issue priority set to: critical
- Issue set to the milestone: 10.4

4 years ago

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

4 years ago

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

4 years ago

[20171025] - Offline Triage ==> 10.6

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

4 years ago

Per 10.5.x/10.6 Triage: FUTURE

ftweedal: precursor to using AES encryption in LWCA key replication

Metadata Update from @mharmsen:
- Issue set to the milestone: FUTURE (was: 10.6)

3 years ago


commit e3afcfd9fa240b52a53310bd72b0e8a6bd30fc14
Author: Fraser Tweedale <ftweedal@redhat.com>
Date:   Wed Jul 24 12:33:46 2019 +1000

    ca-authority-key-export: support AES

    Add support for exporting wrapped private keys using AES128-CBC as
    the symmetric algorithm.

    Fixes: https://pagure.io/dogtagpki/issue/2666

commit 477c4f06fa1041557161241f8aedf36432f02b5e
Author: Fraser Tweedale <ftweedal@redhat.com>
Date:   Wed Jul 24 11:36:01 2019 +1000

    ca-authority-key-export: use random IV

    Part of: https://pagure.io/dogtagpki/issue/2666

commit a47581fe0884074a2ada28366fc4a44d40f443ab
Author: Fraser Tweedale <ftweedal@redhat.com>
Date:   Wed Jul 24 11:26:21 2019 +1000

    ca-authority-key-export: add --algorithm option

    We need to support AES key export, but also require backwards
    compatibility with existing servers that can only import
    DES-EDE3-CBC.  So as a first step, teach the ca-authority-key-export
    command the --algorithm option, which defaults to 1.2.840.113549.3.7
    (DES-EDE3-CBC).  AES support will be added in a subsequent commit.

    Part of: https://pagure.io/dogtagpki/issue/2666

commit e433237aa40075e4c17a1c83c4ef924887f38d16
Author: Fraser Tweedale <ftweedal@redhat.com>
Date:   Wed Jul 24 10:48:23 2019 +1000

    importPKIArchiveOptions: support AES

    CryptoUtil.importPKIArchiveOptions() is used for Lightweight CA
    (LWCA) key import.  Update it to support AES-encrypted keys.  DES
    import remains supported for backwards compatibility.

    Fixes: https://pagure.io/dogtagpki/issue/2777

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:

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.