-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Package Request: audit #1362
Comments
For the first question we need the output of |
Same for the second question, check the issue template text |
See also #461 |
Updated comment regarding |
For the second question, you should to give us the info for each package listed in the answer to the first question. |
Next steps (can be done in parallel):
|
Updated comment referring to size of the |
Hum, we need the info for the |
Of course - updated 😶🌫️ |
IMO, I don't think we should add |
Looking at https://bugzilla.redhat.com/show_bug.cgi?id=1827263 and the |
Context for |
The audit package already includes the following scripts (https://github.com/linux-audit/audit-userspace/tree/master/init.d):
|
|
Flagging for meeting discussion but I won't be here this week so maybe next week. |
Since I was on a course last week, I wonder if there were any debate related to this topic? |
Not yet. There will likely be this week. |
You can check the meeting logs (see the README in this repo) for each meeting. |
Links to existing docs about the |
Past discussion: https://bugzilla.redhat.com/show_bug.cgi?id=1768815 |
We'll have to reach out to the audit maintainers to see which path they would prefer to ideally implement option B. |
Include audit to be able to manage and load rules in the audit subsystem in the kernel. Fixes: coreos/fedora-coreos-tracker#1362
Include audit to be able to manage and load rules in the audit subsystem in the kernel. Fixes: coreos/fedora-coreos-tracker#1362
Include audit to be able to manage and load rules in the audit subsystem in the kernel. Fixes: coreos/fedora-coreos-tracker#1362
Note for when we enable next-devel: we'll have to confirm that |
We want to make sure we never unknowingly start shipping this package. Relevant with the recent addition of audit which used to pull it in: coreos/fedora-coreos-tracker#1362
Opened coreos/fedora-coreos-config#2591 which will guarantee this. :) |
We want to make sure we never unknowingly start shipping this package. Relevant with the recent addition of audit which used to pull it in: coreos/fedora-coreos-tracker#1362
The fix for this went into |
Include audit to be able to manage and load rules in the audit subsystem in the kernel. Fixes: coreos/fedora-coreos-tracker#1362
We want to make sure we never unknowingly start shipping this package. Relevant with the recent addition of audit which used to pull it in: coreos/fedora-coreos-tracker#1362
Include audit to be able to manage and load rules in the audit subsystem in the kernel. Fixes: coreos/fedora-coreos-tracker#1362
We want to make sure we never unknowingly start shipping this package. Relevant with the recent addition of audit which used to pull it in: coreos/fedora-coreos-tracker#1362
The fix for this went into |
The fix for this went into |
What, if any, are the additional dependencies on the package? (i.e. does it pull in Python, Perl, etc)
What is the size of the package and its dependencies?
What problem are you trying to solve with this package? Or what functionality does the package provide?
The audit package contains the user space utilities for storing and searching the audit records generated by the audit subsystem in the Linux 2.6 and later kernels.
Can the software provided by the package be run from a container? Explain why or why not.
Yes, in theory, but it's likely not supported and will probably not work well with host filesystem rules.
Can the tool(s) provided by the package be helpful in debugging container runtime issues?
No
Can the tool(s) provided by the package be helpful in debugging networking issues?
No
Is it possible to layer the package onto the base OS as a day 2 operation? Explain why or why not.
Yes
In the case of packages providing services and binaries, can the packaging be adjusted to just deliver binaries?
TODO: Fill in bugs tracking that from previous issue
Can the tool(s) provided by the package be used to do things we’d rather users not be able to do in FCOS?
N/A
Does the software provided by the package have a history of CVEs?
No
?? https://www.cvedetails.com/product/13730/Linux-Audit.html?vendor_id=33
The text was updated successfully, but these errors were encountered: