Bug 2154242
| Summary: | [Regression] Executing bash from a system cronjob ends up executing as rpm_script_t | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Renaud Métrich <rmetrich> | |
| Component: | selinux-policy | Assignee: | Zdenek Pytela <zpytela> | |
| Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> | |
| Severity: | urgent | Docs Contact: | Petr Hybl <phybl> | |
| Priority: | high | |||
| Version: | 8.7 | CC: | bwelterl, eize.speerstra, jafiala, lvrabec, mmalik, nknazeko, peter.vreman, phybl, zpytela | |
| Target Milestone: | rc | Keywords: | AutoVerified, Triaged | |
| Target Release: | 8.8 | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | selinux-policy-3.14.3-117.el8 | Doc Type: | Bug Fix | |
| Doc Text: |
.`crontab` bash scripts no longer execute in incorrect context
Previously, a bug fix published in erratum link:https://access.redhat.com/errata/RHBA-2022:7691[RHBA-2022:7691] used too general transition rule. Consequently, a bash script executed from the `crontab` file was executed in the `rpm_script_t` context instead of the `system_cronjob_t` context. With this update, bash scripts are now executed in the correct context.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2173685 (view as bug list) | Environment: | ||
| Last Closed: | 2023-05-16 09:04:19 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2173685 | |||
|
Description
Renaud Métrich
2022-12-16 10:50:55 UTC
I've created the BZ as Urgent because there is no workaround: it's not possible to add another transition rule to force staying as system_cronjob_t. 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 (selinux-policy 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-2023:2965 |