Bug 2225222
| Summary: | Ordering matters for permitted_enctypes | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Alexander Sosedkin <asosedki> |
| Component: | crypto-policies | Assignee: | Alexander Sosedkin <asosedki> |
| Status: | CLOSED ERRATA | QA Contact: | Ondrej Moriš <omoris> |
| Severity: | medium | Docs Contact: | Alexandra Nikandrova <anikandr> |
| Priority: | medium | ||
| Version: | 9.3 | CC: | anikandr, gfialova, jrische, mjahoda |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | crypto-policies-20230731-1.git94f0e2c.el9 | Doc Type: | Enhancement |
| Doc Text: |
.`crypto-policies` `permitted_enctypes` no longer break replications in FIPS mode
Before this update, an IdM server running on RHEL 8 sent an AES-256-HMAC-SHA-1-encrypted service ticket that an IdM replica running RHEL 9 in FIPS mode. Consequently, the default `permitted_enctypes` `krb5` configuration broke a replication between the RHEL 8 IdM server and the RHEL 9 IdM replica in FIPS mode.
This update of the system-wide cryptographic policies reorders the `permitted_enctypes` `krb5` configuration option values to allow prioritization of more interoperable encryption types by default. As a result, the `permitted_enctypes` configuration no longer break replications between a RHEL 8 IdM servers and a RHEL 9 IdM replica in FIPS mode.
NOTE: If you use Kerberos, verify the order of the values of `permitted_enctypes` in the `/etc/crypto-policies/back-ends/krb5.config` file. If your scenario requires a different order, apply a custom cryptographic subpolicy.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-11-07 08:53:12 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 2
Alexander Sosedkin
2023-07-24 17:18:40 UTC
I approved both these pull requests: https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/merge_requests/139 https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/merge_requests/140 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 (crypto-policies 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/RHEA-2023:6630 |