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.
DescriptionAlexander Bokovoy
2020-06-26 15:01:22 UTC
Upstream merge request: https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/merge_requests/70
Add AD-SUPPORT policy module that can be used by administrators to add RC4
ciphers back to the supported list with
update-crypto-policies --set DEFAULT:AD-SUPPORT
There is no need to enable AD-SUPPORT by default but FreeIPA and Samba will
benefit from the presence of this policy module and handle enablement
automatically in case it is needed.
RC4 cipher is widely used in Active Directory environment.
For all AD environments since Windows Server 2008:
- default encryption type for users and services is still RC4 despite allowing to enable AES encryption.
- changing forest- or domain-wide policy to enable AES encryption types does not change existing user and services' Kerberos keys. They still have only RC4 unless they changed user password or machine account password.
- when trust is established between AD domains in the same forest, default encryption type for trusted domain object (krbtgt/...) is RC4 only, unless there is a forest- or domain-wide policy to enable AES encryption type is in action.
- removing RC4 from the policy in AD leads to situation that no Kerberos ticket can be issued at all.
Alexander, can your team help us to check that everything works as expected once the fix is available? Having a sign-off from you in this BZ would definitely help.
Comment 3Alexander Bokovoy
2020-06-29 10:11:32 UTC
Verified SanityOnly.
NEW (crypto-policies-20200629-1.git806b5d3.el8)
===============================================
# update-crypto-policies --show
DEFAULT
# cat /etc/crypto-policies/back-ends/krb5.config
[libdefaults]
permitted_enctypes = aes256-cts-hmac-sha1-96 aes256-cts-hmac-sha384-192 camellia256-cts-cmac aes128-cts-hmac-sha1-96 aes128-cts-hmac-sha256-128 camellia128-cts-cmac
# update-crypto-policies --set DEFAULT:AD-SUPPORT
Setting system policy to DEFAULT:AD-SUPPORT
Note: System-wide crypto policies are applied on application start-up.
It is recommended to restart the system for the change of policies
to fully take place.
# cat /etc/crypto-policies/back-ends/krb5.config
[libdefaults]
permitted_enctypes = aes256-cts-hmac-sha1-96 aes256-cts-hmac-sha384-192 camellia256-cts-cmac aes128-cts-hmac-sha1-96 aes128-cts-hmac-sha256-128 camellia128-cts-cmac arcfour-hmac-md5
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-2020:4536