Bug 1919155
| Summary: | crypto-policies incorrectly "advertise" Camellia | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Thorsten Scherf <tscherf> |
| Component: | crypto-policies | Assignee: | Alexander Sosedkin <asosedki> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | unspecified | Docs Contact: | Mirek Jahoda <mjahoda> |
| Priority: | high | ||
| Version: | 8.3 | CC: | asosedki, byodlows, fdvorak, hkario, jjelen, lmanasko, mjahoda, omoris, pvrabec, rhel-docs, rrelyea |
| Target Milestone: | rc | Keywords: | Documentation, Triaged |
| Target Release: | 8.0 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-08 16:20:03 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: | |||
|
Description
Thorsten Scherf
2021-01-22 09:44:53 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;). |