All of lore.kernel.org
 help / color / mirror / Atom feed
From: guido@trentalancia.net (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 2/2] system/modutils: Allow kmod to use the sys_admin cap
Date: Mon, 28 Nov 2016 23:08:37 +0100	[thread overview]
Message-ID: <1480370917.14631.16.camel@trentalancia.net> (raw)
In-Reply-To: <20161128230320.158d4202@gentp.lnet>

On Sun, 28/11/2016 at 23.03 +0100, Luis Ressel wrote:
> On Mon, 28 Nov 2016 18:02:56 +0100
> Guido Trentalancia via refpolicy <refpolicy@oss.tresys.com> wrote:

[...]

> I do of course agree that unconditionally adding grsec-specific
> permissions to the refpolicy isn't optimal either.
> 
> What are your thoughts about adding a new kernel_grsec ifdef, similar
> to our current distro_* ifdef's? It would apply to the getty_t
> permission I mentioned earlier, to the kmod_t capability discussed in
> this thread (as soon as we've confirmed it is indeed grsec-related),
> and to any other grsec-specific permissions we've added in the past
> (@Sven, Jason: Do you remember any such permissions?).

Yes, that's the way forward.

> The vast majority of refpolicy+grsec users are probably gentoo folks,
> so we could keep these permissions in ifdef(distro_gentoo) blocks,
> too;

Enclosing them in double ifdef should not be necessary. In my opinion,
the former proposal is enough (ifdef grsecurity).

> but I think that wouldn't be ideal. After all, there may well be
> other
> people using this particular combination; it's not gentoo-specific.

I really look forward to seeing the optimized patches !

Regards,

Guido

  reply	other threads:[~2016-11-28 22:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27 16:41 [refpolicy] [PATCH 1/2] system/modutils: Add kernel_search_key(kmod_t) Luis Ressel
2016-11-27 16:41 ` [refpolicy] [PATCH 2/2] system/modutils: Allow kmod to use the sys_admin cap Luis Ressel
2016-11-27 20:33   ` Guido Trentalancia
2016-11-27 21:22     ` Luis Ressel
2016-11-27 21:55       ` Luis Ressel
2016-11-27 22:30       ` Luis Ressel
2016-11-27 22:31       ` Guido Trentalancia
2016-11-27 22:50         ` Luis Ressel
2016-11-28 17:02           ` Guido Trentalancia
2016-11-28 21:48             ` Luis Ressel
2016-11-28 21:57               ` Guido Trentalancia
2016-11-28 22:14                 ` Luis Ressel
2016-11-28 22:24                   ` Guido Trentalancia
2016-11-28 23:03                     ` Luis Ressel
2016-11-28 23:16                       ` Guido Trentalancia
2016-11-29  1:55                         ` Chris PeBenito
2016-11-29  6:22                           ` Nicolas Iooss
2016-11-29 12:53                             ` [refpolicy] [PATCH] Allow getty the sys_admin capability (was Re: [PATCH 2/2] system/modutils: Allow kmod to use the sys_admin cap) Guido Trentalancia
2016-11-28 22:03             ` [refpolicy] [PATCH 2/2] system/modutils: Allow kmod to use the sys_admin cap Luis Ressel
2016-11-28 22:08               ` Guido Trentalancia [this message]
2016-12-04 23:56 ` [refpolicy] [PATCH 1/2] system/modutils: Add kernel_search_key(kmod_t) Luis Ressel
2016-12-07  0:59 ` Chris PeBenito

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=1480370917.14631.16.camel@trentalancia.net \
    --to=guido@trentalancia.net \
    --cc=refpolicy@oss.tresys.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.