Bug 2021362
| Summary: | Need to update language to be inclusive | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Bob Relyea <rrelyea> |
| Component: | ca-certificates | Assignee: | Bob Relyea <rrelyea> |
| Status: | CLOSED ERRATA | QA Contact: | Ivan Nikolchev <inikolch> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9.0 | CC: | inikolch |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ca-certificates-2020.2.50-94.el9 | Doc Type: | No Doc Update |
| Doc Text: |
This updates the manpages about where p11kit looks for certificates to block when verifying, and removes the old directory. We don't need any doc update for the ca-certificate patch, but we do need to have a note about the pk11kit change.
The old directory was /usr/share/pki/ca-trust-source/blacklist
and the new directory is /usr/share/pki/ca-trust-source/blocklist. The former is a more descriptive name for the purpose of the directory. Customers who perviously put certificates in the former must move them to the latter. This change was already made in p11kit 2.4, The ca-certificate patch only updates the shipped documentation as removes the former directory from it's supplied directories (so the documentation should already be updated).
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-17 15:57:21 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
Bob Relyea
2021-11-09 00:20:11 UTC
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 (new packages: ca-certificates), 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-2022:3976 |