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.
Bug 1919155 - crypto-policies incorrectly "advertise" Camellia
Summary: crypto-policies incorrectly "advertise" Camellia
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: crypto-policies
Version: 8.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: 8.0
Assignee: Alexander Sosedkin
QA Contact: BaseOS QE Security Team
Mirek Jahoda
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-22 09:44 UTC by Thorsten Scherf
Modified: 2022-03-08 16:20 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
.`crypto-policies` incorrectly allow Camellia ciphers The RHEL 8 system-wide cryptographic policies should disable Camellia ciphers in all policy levels, as stated in the product documentation. However, the Kerberos protocol enables the ciphers by default. To work around the problem, apply the `NO-CAMELLIA` subpolicy: ---- # update-crypto-policies --set DEFAULT:NO-CAMELLIA ---- In the previous command, replace `DEFAULT` with the cryptographic level name if you have switched from `DEFAULT` previously. As a result, Camellia ciphers are correctly disallowed across all applications that use system-wide crypto policies only when you disable them through the workaround.
Clone Of:
Environment:
Last Closed: 2022-03-08 16:20:03 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Thorsten Scherf 2021-01-22 09:44:53 UTC 
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/using-the-system-wide-cryptographic-policies_security-hardening

Section Number and Name: 
3.1. System-wide cryptographic policies

Describe the issue: 
In section 'Cipher suites and protocols disabled in all policy levels' we list list the 'Camellia' cipher which would imply that the cipher is not shipped with any of the policies.

But looking at the policies, we can see the cipher is used in all policies except FIPS policy:

 # grep -ri camellia /usr/share/crypto-policies/policies/
/usr/share/crypto-policies/policies/DEFAULT.pol:# non-TLS Ciphers: as TLS Ciphers with added Camellia
/usr/share/crypto-policies/policies/DEFAULT.pol:cipher = AES-256-GCM AES-256-CCM CHACHA20-POLY1305 CAMELLIA-256-GCM \
/usr/share/crypto-policies/policies/DEFAULT.pol:    AES-256-CTR AES-256-CBC CAMELLIA-256-CBC AES-128-GCM AES-128-CCM \
/usr/share/crypto-policies/policies/DEFAULT.pol:    CAMELLIA-128-GCM AES-128-CTR AES-128-CBC CAMELLIA-128-CBC
/usr/share/crypto-policies/policies/FUTURE.pol:# non-TLS Ciphers: same as TLS Ciphers with added non AE ciphers and Camellia
/usr/share/crypto-policies/policies/FUTURE.pol:cipher = AES-256-GCM AES-256-CCM CHACHA20-POLY1305 CAMELLIA-256-GCM \
/usr/share/crypto-policies/policies/FUTURE.pol:    AES-256-CTR AES-256-CBC CAMELLIA-256-CBC
/usr/share/crypto-policies/policies/LEGACY.pol:# non-TLS Ciphers: as TLS Ciphers with added Camellia
/usr/share/crypto-policies/policies/LEGACY.pol:cipher = AES-256-GCM AES-256-CCM CHACHA20-POLY1305 CAMELLIA-256-GCM \
/usr/share/crypto-policies/policies/LEGACY.pol:    AES-256-CTR AES-256-CBC CAMELLIA-256-CBC AES-128-GCM AES-128-CCM \
/usr/share/crypto-policies/policies/LEGACY.pol:    CAMELLIA-128-GCM AES-128-CTR AES-128-CBC CAMELLIA-128-CBC \
/usr/share/crypto-policies/policies/modules/NO-CAMELLIA.pmod:# This is example policy dropping the Camellia support altogether
/usr/share/crypto-policies/policies/modules/NO-CAMELLIA.pmod:tls_cipher = -CAMELLIA-256-GCM -CAMELLIA-256-CBC -CAMELLIA-128-GCM \
/usr/share/crypto-policies/policies/modules/NO-CAMELLIA.pmod:    -CAMELLIA-128-CBC
/usr/share/crypto-policies/policies/modules/NO-CAMELLIA.pmod:cipher = -CAMELLIA-256-GCM -CAMELLIA-256-CBC -CAMELLIA-128-GCM \
/usr/share/crypto-policies/policies/modules/NO-CAMELLIA.pmod:    -CAMELLIA-128-CBC

As we can see, there is even a 'NO-CAMELLIA' policy to explicitly disable the cipher.

Suggestions for improvement: 
Remove 'Camellia' from the section 'Cipher suites and protocols disabled in all policy levels'.

Additional information:
Comment 7 Bob Relyea 2021-01-26 19:08:36 UTC 
We should removed Camella from NORMAL and FUTURE at least. NSS application could still turn Camella on, but it's off be default already, so it probably shouldn't be on by policy anymore. We should also talk about seed;).
Note You need to log in before you can comment on or make changes to this bug.