From: Petr Lautrbach <plautrba@redhat.com>
To: "Christian Göttsche" <cgzones@googlemail.com>,
"James Carter" <jwcart2@gmail.com>,
"SElinux list" <selinux@vger.kernel.org>
Subject: Re: [PATCH] checkpolicy: error out if required permission would exceed limit
Date: Tue, 21 Jun 2022 15:23:16 +0200 [thread overview]
Message-ID: <87ilourvzv.fsf@redhat.com> (raw)
In-Reply-To: <CAJ2a_Df8QY92WENiLMcpiayr_QgJP-pyckb5XWcsb-i8YjhqVA@mail.gmail.com>
Christian Göttsche <cgzones@googlemail.com> writes:
> On Wed, 15 Jun 2022 at 20:18, James Carter <jwcart2@gmail.com> wrote:
>>
>> On Fri, Jun 10, 2022 at 11:12 AM Christian Göttsche
>> <cgzones@googlemail.com> wrote:
>> >
>> > A require statement for a class permission adds that permission to the
>> > class representation for the current module. In case the resulting
>> > class would have more than the supported amount of 32 permissions
>> > assigned the resulting binary module will fail to load at link-time
>> > without an informative error message (since [1]).
>> >
>> > Bail out if adding a permission would result in a class having more then
>
> s/then/than/
Merged, thanks!
>> > the supported amount of 32 permissions assigned.
>> >
>> > [1]: https://github.com/SELinuxProject/selinux/commit/97af65f69644a3233d073ae93980a0d2e51f42e1
>> >
>> > Closes: https://github.com/SELinuxProject/selinux/issues/356
>> > Reported-by: Julie Pichon
>> > Signed-off-by: Christian Göttsche <cgzones@googlemail.com>
>>
>> Acked-by: James Carter <jwcart2@gmail.com>
>>
>> > ---
>> > checkpolicy/module_compiler.c | 8 ++++++++
>> > 1 file changed, 8 insertions(+)
>> >
>> > diff --git a/checkpolicy/module_compiler.c b/checkpolicy/module_compiler.c
>> > index 129650fa..3188af89 100644
>> > --- a/checkpolicy/module_compiler.c
>> > +++ b/checkpolicy/module_compiler.c
>> > @@ -851,6 +851,14 @@ int require_class(int pass)
>> > free(perm_id);
>> > return -1;
>> > }
>> > + if (datum->permissions.nprim >= PERM_SYMTAB_SIZE) {
>> > + yyerror2("Class %s would have too many permissions "
>> > + "to fit in an access vector with permission %s",
>> > + policydbp->p_class_val_to_name[datum->s.value - 1],
>> > + perm_id);
>> > + free(perm_id);
>> > + return -1;
>> > + }
>> > allocated = 1;
>> > if ((perm = malloc(sizeof(*perm))) == NULL) {
>> > yyerror("Out of memory!");
>> > --
>> > 2.36.1
>> >
prev parent reply other threads:[~2022-06-21 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 15:06 [PATCH] checkpolicy: error out if required permission would exceed limit Christian Göttsche
2022-06-15 18:18 ` James Carter
2022-06-15 18:31 ` Christian Göttsche
2022-06-21 13:23 ` Petr Lautrbach [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=87ilourvzv.fsf@redhat.com \
--to=plautrba@redhat.com \
--cc=cgzones@googlemail.com \
--cc=jwcart2@gmail.com \
--cc=selinux@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox