From: Anurag Aggarwal <anurag19aggarwal@gmail.com>
To: Paul Moore <paul@paul-moore.com>, sgrubb@redhat.com
Cc: tibdewal.rahulkumar@gmail.com, Linux-audit@redhat.com
Subject: Re: Key based rate limiter (audit_set_rate_limit)
Date: Thu, 9 Mar 2023 11:46:27 +0530 [thread overview]
Message-ID: <CAPoNrtsZv96hz-E=nU8y2KSxhqU8vEfcVKQH6X=EqD3O0BmLwA@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhRGFL8MDtNXbSoes-gV=qM3YmCU20=UQoCfR29nnU7dcA@mail.gmail.com>
>
> However, I am fairly skeptical that we could add per-key rate limiting
> without introducing a non-trivial amount of overhead to record
> generation, which would be a show stopper for this feature given its
> expected limited appeal.
>
I understand the reservation. I will spend some time to analyze it impact
Steve, about your comment:
> There just really isn't room to add more thinkgs without some userspace API
> problem. (This would definitely need a feaure bitmap so user space can make
> sense of it.)
I was not aware that this could cause problems in the userspace API.
Key based filtering for rate limiting could be a useful feature. It is
something that would
help us a lot.
--
Anurag Aggarwal
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2023-03-09 6:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 10:53 Key based rate limiter (audit_set_rate_limit) Anurag Aggarwal
2023-02-28 14:11 ` Paul Moore
2023-02-28 15:35 ` Anurag Aggarwal
2023-02-28 16:31 ` Paul Moore
2023-02-28 17:03 ` Lenny Bruzenak
2023-03-01 15:31 ` Anurag Aggarwal
2023-03-01 17:05 ` Lenny Bruzenak
2023-03-02 5:13 ` Anurag Aggarwal
2023-03-02 17:24 ` Lenny Bruzenak
2023-03-02 19:11 ` Paul Moore
2023-03-06 5:48 ` Anurag Aggarwal
2023-03-08 11:53 ` Anurag Aggarwal
2023-03-08 15:51 ` Steve Grubb
2023-03-08 17:04 ` Paul Moore
2023-03-09 6:16 ` Anurag Aggarwal [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPoNrtsZv96hz-E=nU8y2KSxhqU8vEfcVKQH6X=EqD3O0BmLwA@mail.gmail.com' \
--to=anurag19aggarwal@gmail.com \
--cc=Linux-audit@redhat.com \
--cc=paul@paul-moore.com \
--cc=sgrubb@redhat.com \
--cc=tibdewal.rahulkumar@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.