Red Hat Bugzilla – Bug 446707
Add support for filetype option in audit subsystem
Last modified: 2009-01-20 15:07:59 EST
Description of problem:
Al Viro submitted a patch that gives another option to have audit rules trigger
on a specific kind of file. I think he said it was commit
8b67dca9420474623709e00d72a066068a502b20 in mainline kernel.
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Unfortunately the previous automated notification about the
non-inclusion of this request in Red Hat Enterprise Linux 5.3 used
the wrong text template. It should have read: this request has been
reviewed by Product Management and is not planned for inclusion
in the current minor release of Red Hat Enterprise Linux.
If you would like this request to be reviewed for the next minor
release, ask your support representative to set the next rhel-x.y
flag to "?" or raise an exception.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
You can download this test kernel from http://people.redhat.com/dzickus/el5
This bug (feature request) has been marked for inclusion in the Red Hat Enterprise Linux 5.3 Release Notes.
To aid in the development of relevant and accurate release notes, please fill out the "Release Notes" field above with the following 4 pieces of information:
Cause: What actions or circumstances induced the feature request.
Consequence: What action was inhibited by the feature's absence.
Fix: What was done to implement the feature.
Result: now happens when the actions or circumstances above occur. (NB: this is not the same as 'the feature request was fulfilled')
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.