6:12 p.m.
Hi, I am running auditd-3.0.7-4 on an Alma Linux v8.8.
I know that for all of RHEL 6 and RHEL 7 variants that I worked with, to
include CentOS (not Stream) that after I rebooted a server or restarted the
auditd service (with -e 1 set) that I would 100% of the time get a report
in /var/log/messages about the quantity of rules that successfully loaded.
I could compare that to my unified rules file
(/etc/audit/rules.d/Unified.rules - for a reference) and strip out the
typical for auditd Control rules (-D, -e 1, -f 1, -b, -r, for examples) and
then assess if I had the full set of files loaded or not.
With this implementation of auditd, on version 3.0.7-4, I am not getting
those results anymore.
Am I looking in the wrong place, because for me this is important
information?
Yes, I know that I can also manually execute "auditctl -l | wc -l" and get
that information too, but I was wondering if this is planned or if I am
looking in the wrong place, or what to do.
Thanks,
--------------------------
Warron French
9:42 a.m.
Hello Warron,
On Tuesday, May 23, 2023 7:12:07 PM EDT warron.french wrote:
Hi, I am running auditd-3.0.7-4 on an Alma Linux v8.8.
I know that for all of RHEL 6 and RHEL 7 variants that I worked with, to
include CentOS (not Stream) that after I rebooted a server or restarted the
auditd service (with -e 1 set) that I would 100% of the time get a report
in /var/log/messages about the quantity of rules that successfully loaded.
It has never done that unless someone else has a patch they did not send
upstream.
I could compare that to my unified rules file
(/etc/audit/rules.d/Unified.rules - for a reference) and strip out the
typical for auditd Control rules (-D, -e 1, -f 1, -b, -r, for examples) and
then assess if I had the full set of files loaded or not.
With this implementation of auditd, on version 3.0.7-4, I am not getting
those results anymore.
Am I looking in the wrong place, because for me this is important
information?
It has never done that. auditctl -D gives the output of auditctl -s as a
convenience. But auditctl -s has never reported how many rules are loaded. I
don't think the kernel has a counter. It has a variable for if any rules are
loaded, but not the quantity.
Yes, I know that I can also manually execute "auditctl -l | wc
-l" and get
that information too, but I was wondering if this is planned or if I am
looking in the wrong place, or what to do.
It has never done that and is not planned.
-Steve
3:01 p.m.
On 2023-05-24 10:42, Steve Grubb wrote:
Hello Warron,
On Tuesday, May 23, 2023 7:12:07 PM EDT warron.french wrote:
> Hi, I am running auditd-3.0.7-4 on an Alma Linux v8.8.
>
> I know that for all of RHEL 6 and RHEL 7 variants that I worked with, to
> include CentOS (not Stream) that after I rebooted a server or restarted the
> auditd service (with -e 1 set) that I would 100% of the time get a report
> in /var/log/messages about the quantity of rules that successfully loaded.
It has never done that unless someone else has a patch they did not send
upstream.
> I could compare that to my unified rules file
> (/etc/audit/rules.d/Unified.rules - for a reference) and strip out the
> typical for auditd Control rules (-D, -e 1, -f 1, -b, -r, for examples) and
> then assess if I had the full set of files loaded or not.
>
> With this implementation of auditd, on version 3.0.7-4, I am not getting
> those results anymore.
> Am I looking in the wrong place, because for me this is important
> information?
It has never done that. auditctl -D gives the output of auditctl -s as a
convenience. But auditctl -s has never reported how many rules are loaded. I
don't think the kernel has a counter. It has a variable for if any rules are
loaded, but not the quantity.
Minor correction: there is a kernel variable (audit_n_rules) that counts
the number of syscall rules in place, but it isn't reported directly
outside the kernel. This feeds the boolean (struct
audit_context)->dummy.
> Yes, I know that I can also manually execute "auditctl -l
| wc -l" and get
> that information too, but I was wondering if this is planned or if I am
> looking in the wrong place, or what to do.
It has never done that and is not planned.
-Steve
- RGB
--
Richard Guy Briggs <rgb(a)redhat.com>
Sr. S/W Engineer, Kernel Security, Base Operating Systems
Remote, Ottawa, Red Hat Canada
IRC: rgb, SunRaycer
Voice: +1.647.777.2635, Internal: (81) 32635
7:41 p.m.
Obviously both of you are correct. I am thinking about the number of rules
that load when not all of the rules load. Specifically, it gives a line
number of the last line that loaded from the rules. Which, for
troubleshooting purposes, I always put into a single file and sort
"alphabetically."
Also, I solved my own problem on the ruleset in the single file I was
working with on my VM. I had 220 lines of syntax, and many of the lines
were auditd controls, because I do not know the exact term to label them;
things like -D -b -e -f and so on.
Thank you both, sorry for the disruption.
--------------------------
Warron French
On Wed, May 24, 2023 at 4:01 PM Richard Guy Briggs <rgb(a)redhat.com> wrote:
On 2023-05-24 10:42, Steve Grubb wrote:
> Hello Warron,
>
> On Tuesday, May 23, 2023 7:12:07 PM EDT warron.french wrote:
> > Hi, I am running auditd-3.0.7-4 on an Alma Linux v8.8.
> >
> > I know that for all of RHEL 6 and RHEL 7 variants that I worked with,
to
> > include CentOS (not Stream) that after I rebooted a server or
restarted the
> > auditd service (with -e 1 set) that I would 100% of the time get a
report
> > in /var/log/messages about the quantity of rules that successfully
loaded.
>
> It has never done that unless someone else has a patch they did not send
> upstream.
>
> > I could compare that to my unified rules file
> > (/etc/audit/rules.d/Unified.rules - for a reference) and strip out the
> > typical for auditd Control rules (-D, -e 1, -f 1, -b, -r, for
examples) and
> > then assess if I had the full set of files loaded or not.
> >
> > With this implementation of auditd, on version 3.0.7-4, I am not
getting
> > those results anymore.
> > Am I looking in the wrong place, because for me this is important
> > information?
>
> It has never done that. auditctl -D gives the output of auditctl -s as a
> convenience. But auditctl -s has never reported how many rules are
loaded. I
> don't think the kernel has a counter. It has a variable for if any rules
are
> loaded, but not the quantity.
Minor correction: there is a kernel variable (audit_n_rules) that counts
the number of syscall rules in place, but it isn't reported directly
outside the kernel. This feeds the boolean (struct
audit_context)->dummy.
> > Yes, I know that I can also manually execute "auditctl -l | wc -l"
and get
> > that information too, but I was wondering if this is planned or if I
am
> > looking in the wrong place, or what to do.
>
> It has never done that and is not planned.
>
> -Steve
- RGB
--
Richard Guy Briggs <rgb(a)redhat.com>
Sr. S/W Engineer, Kernel Security, Base Operating Systems
Remote, Ottawa, Red Hat Canada
IRC: rgb, SunRaycer
Voice: +1.647.777.2635, Internal: (81) 32635
--
Linux-audit mailing list
Linux-audit(a)redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
575
days inactive
578
days old
linux-audit@lists.linux-audit.osci.io
3 comments
3 participants
participants (3)
-
Richard Guy Briggs -
Steve Grubb -
warron.french