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.

Derived properties like `tls_cipher` are not affected by follow-up modifications of `cipher`,
confusing users (example: bz1933036).
Best way forward is to move away from them to a more coherently inheritable `cipher@TLS`
that is affected by `cipher` modifications. The support is now landed upstream.

Known QE concerns:
1) The parser is heavily rewritten. quite some upstream tests were added,
   but it wouldn't hurt to improve downstream coverage of malformed configs as well
2) This is new functionality anyway, we better at least smoke-test it downstream
3) Error/warning reporting was heavily redone.
   I've tried to keep it as close as possible to what was there,
   but somebody should have a look at it anyway.
   (see) -/Sanity/bad-policies
4) We should test that bz1933036 is now achievable by a mere `cipher = -*-CBC` =)

Known docs/backwards-compat concerns:
1) Old properties are still accepted and applied separately at the end of the policy,
   and print warnings suggesting to use new options,
   but rectifying the broken diamond inheritance can't happen without breaking backwards compat.
   We'll definitely need to have the need to review and migrate custom (sub)policies
   documented in release notes
   (draft: https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/merge_requests/92#note_571831205).

*** Bug 1933036 has been marked as a duplicate of this bug. ***

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/RHBA-2021:4460