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 1939379 - Rebase FAPOLICYD to the latest upstream version
Summary: Rebase FAPOLICYD to the latest upstream version
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2021-12-07
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: fapolicyd
Version: 8.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Radovan Sroka
QA Contact: Dalibor Pospíšil
Mirek Jahoda
URL:
Whiteboard:
Depends On:
Blocks: 2032408
TreeView+ depends on / blocked
 
Reported: 2021-03-16 09:26 UTC by Radovan Sroka
Modified: 2022-05-10 14:41 UTC (History)
2 users (show)

Fixed In Version: fapolicyd-1.1-1.el8
Doc Type: Enhancement
Doc Text:
.`fapolicyd` rebased to 1.1 The `fapolicyd` packages have been upgraded to the upstream version 1.1, which contains many improvements and bug fixes. Most notable changes include the following: * The `/etc/fapolicyd/rules.d/` directory for files containing allow and deny execution rules replaces the `/etc/fapolicyd/fapolicyd.rules` file. The `fagenrules` script now merges all component rule files in this directory to the `/etc/fapolicyd/compiled.rules` file. See the new `fagenrules(8)` man page for more details. * In addition to the `/etc/fapolicyd/fapolicyd.trust` file for marking files outside of the RPM database as trusted, you can now use the new `/etc/fapolicyd/trust.d` directory, which supports separating a list of trusted files into more files. You can also add an entry for a file by using the `fapolicyd-cli -f` subcommand with the `--trust-file` directive to these files. See the `fapolicyd-cli(1)` and `fapolicyd.trust(13)` man pages for more information. * The `fapolicyd` trust database now supports white spaces in file names. * `fapolicyd` now stores the correct path to an executable file when it adds the file to the trust database.
Clone Of:
: 2032408 (view as bug list)
Environment:
Last Closed: 2022-05-10 14:13:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:1898 0 None None None 2022-05-10 14:14:06 UTC

Comment 15 errata-xmlrpc 2022-05-10 14:13:54 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 (Moderate: fapolicyd security, 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/RHSA-2022:1898


Note You need to log in before you can comment on or make changes to this bug.