Bug 2100087 - rebase fapolicyd to the latest stable vesion
Summary: rebase fapolicyd to the latest stable vesion
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: fapolicyd
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Radovan Sroka
QA Contact: Dalibor Pospíšil
Mirek Jahoda
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-22 12:06 UTC by Radovan Sroka
Modified: 2022-11-08 10:53 UTC (History)
1 user (show)

Fixed In Version: fapolicyd-1.1.3-8.el8
Doc Type: Enhancement
Doc Text:
.`fapolicyd` rebased to 1.1.3 The `fapolicyd` packages have been upgraded to version 1.1.3. Notable improvements and bug fixes include: * Rules can now contain the new subject PPID attribute, which matches the parent PID (process ID) of a subject. * The OpenSSL library replaced the Libgcrypt library as a cryptographic engine for hash computations. * The `fagenrules --load` command now works correctly.
Clone Of:
Environment:
Last Closed: 2022-11-08 09:51:54 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-125975 0 None None None 2022-06-22 12:11:52 UTC
Red Hat Issue Tracker SECENGSP-4651 0 None None None 2022-06-22 12:11:54 UTC
Red Hat Product Errata RHBA-2022:7627 0 None None None 2022-11-08 09:52:07 UTC

Description Radovan Sroka 2022-06-22 12:06:31 UTC 
This bug was initially created as a copy of Bug #2100041

I am copying this bug because: 



Please, rebase fapolicyd to the latest stable version 1.1.3.

The release contains several performance related patches and sighup handling.
Comment 19 errata-xmlrpc 2022-11-08 09:51: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 (fapolicyd 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-2022:7627
Note You need to log in before you can comment on or make changes to this bug.