On 2021-03-19 13:52, Phil Sutter wrote: > On Thu, Mar 18, 2021 at 02:37:03PM -0400, Richard Guy Briggs wrote: > > On 2021-03-18 17:30, Phil Sutter wrote: > [...] > > > Why did you leave the object-related logs in place? They should reappear > > > at commit time just like chains and sets for instance, no? > > > > There are other paths that can trigger these messages that don't go > > through nf_tables_commit() that affect the configuration data. The > > counters are considered config data for auditing purposes and the act of > > resetting them is audittable. And the only time we want to emit a > > record is when they are being reset. > > Oh, I see. I wasn't aware 'nft reset' bypasses the transaction logic, > thanks for clarifying!
That's my current understanding. If someone else has a better understanding I'd be grateful if they could correct me. > Cheers, Phil - RGB -- Richard Guy Briggs <r...@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@redhat.com https://listman.redhat.com/mailman/listinfo/linux-audit