Bug 1897092
Summary: | fapolicyd breaks system upgrade, leaving system in dead state - complete fix [rhel-8.1.0.z] | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | RHEL Program Management Team <pgm-rhel-tools> |
Component: | fapolicyd | Assignee: | Radovan Sroka <rsroka> |
Status: | CLOSED ERRATA | QA Contact: | Dalibor Pospíšil <dapospis> |
Severity: | urgent | Docs Contact: | Jan Fiala <jafiala> |
Priority: | urgent | ||
Version: | 8.3 | CC: | amdas, bfinger, bhoefer, cchen, cww, dapospis, dasmokedog, emcnabb, jamills, jpazdziora, jss, jwboyer, klaas, ktordeur, mthacker, nkinder, pgregorycullen, qe-baseos-security, qguo, rblakley, rmetrich, rmullett, rsroka, seldridg, thomas.juberg, xiliang, yuokada |
Target Milestone: | rc | Keywords: | Triaged, ZStream |
Target Release: | 8.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | fapolicyd-0.8.10-3.el8_1.6 | Doc Type: | Bug Fix |
Doc Text: |
.`fapolicyd` no longer prevents RHEL updates
When an update replaces the binary of a running application, the kernel modifies the application binary path in memory by appending the ` (deleted)` suffix. Previously, the `fapolicyd` file access policy daemon treated such applications as untrusted, and prevented them from opening and executing any other files. As a consequence, the system was sometimes unable to boot after applying updates.
With this update, `fapolicyd` ignores the suffix in the binary path so the binary can match the trust database. As a result, `fapolicyd` enforces the rules correctly and the update process can finish.
|
Story Points: | --- |
Clone Of: | 1896875 | Environment: | |
Last Closed: | 2020-11-30 10:18:44 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1896875 | ||
Bug Blocks: |
Comment 1
Lukas Vrabec
2020-11-12 10:05:29 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 (fapolicyd bug fix 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:5241 |