Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionFlorence Blanc-Renaud
2022-11-22 07:25:28 UTC
Cloned from upstream: https://pagure.io/freeipa/issue/9259
### Issue
AES-128-CBC was recently enabled as default wrapping algorithm for transport of secrets.
This change was done in favor of FIPS as crypto-policies disabled 3DES in RHEL9, but
setting AES as default ended-up breaking backwards compatibility with older RHEL systems.
#### Steps to Reproduce
1. spawn a topology with a rhel7.9 server, and a rhel8.7 client
2. add a vault from the client: "ipa vault-add vault"
#### Actual behavior
Client fails with: "ipa: ERROR: an internal error has occurred", for other combinations you could see: "ipa: ERROR: Unknown option: wrapping_algo"
Without FIPS:
oldServer + newReplica + newClient
client fails with: "ipa: ERROR: Unknown option: wrapping_algo"
replica works
master works
newServer + oldClient:
client fails with: "ipa: ERROR: an internal error has occurred"
server works
with FIPS:
oldServer + newReplica + newClient:
client fails with: "ipa: ERROR: Unknown option: wrapping_algo"
replica works
master works
newServer + oldClient:
client fails with: "ipa: ERROR: an internal error has occurred"
server works
where old is RHEL7 and new is RHEL8
#### Expected behavior
ipa vaults work when running in mixed topologies.
#### Additional info:
The new wrapping algo implementation:
40c362e1eeb000867d0e6244ce03b66b6a35e913
"Support AES for KRA archival wrapping"
introduced a new option "--wrapping-algorithm" for "ipa vault-[retrieve/archive]" that is supposed to be internal only, actually it doesn't work. It should be hidden.
Comment 1Florence Blanc-Renaud
2022-11-22 07:26:57 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (idm:client and idm:DL1 bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:2794