From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 5/8] Dontaudit getsched on all domains
Date: Fri, 21 Dec 2012 21:17:39 +0100 [thread overview]
Message-ID: <20121221201739.GA6960@siphos.be> (raw)
In-Reply-To: <20121217102603.GA1030@siphos.be>
On Mon, Dec 17, 2012 at 11:26:04AM +0100, Sven Vermeulen wrote:
> > > --- a/policy/modules/system/userdomain.if
> > > +++ b/policy/modules/system/userdomain.if
> > > @@ -523,6 +523,8 @@ template(`userdom_common_user_template',`
> > > dev_read_sound_mixer($1_t)
> > > dev_write_sound_mixer($1_t)
> > >
> > > + domain_dontaudit_getsched_all_domains($1_t)
> >
> > That is too coarse in my view.
> >
> > This will also dontaudit legitimate access for processes needing this
> > running in the user domain.
> >
> > Lets say i have this app that depends on this permission for itself:
> >
> > allow staff_t self:process { signal getsched };
> >
> > Then this rule will silently hide that access
>
> I understand that, but the other method would be to create
> *_dontaudit_getsched for each and every possible module, and add it in the
> user domain definition fully loaded with optional_policy() statements.
>
> And if the user domain doesn't need getsched itself, then running htop will
> generate denials anyhow for self (i.e. in your above example, you'll get
> denials for staff_t getsched on itself) so eventually you'll add in a
> staff_dontaudit_getsched() for that too?
>
> Another alternative could be to run htop in its own domain, but that doesn't
> make sense imo...
Chris, what is your take on this?
Wkr,
Sven Vermeulen
next prev parent reply other threads:[~2012-12-21 20:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 9:42 [refpolicy] [PATCH 0/8] Updates on master (non-contrib) Sven Vermeulen
2012-12-17 9:42 ` [refpolicy] [PATCH 1/8] Postgresql 9.2 connects to its unix stream socket Sven Vermeulen
2013-01-03 15:30 ` Christopher J. PeBenito
2012-12-17 9:42 ` [refpolicy] [PATCH 2/8] lvscan creates the /run/lock/lvm directory if nonexisting (v2) Sven Vermeulen
2013-01-03 15:30 ` Christopher J. PeBenito
2012-12-17 9:42 ` [refpolicy] [PATCH 3/8] Allow syslogger to manage cron log files (v2) Sven Vermeulen
2013-01-03 15:31 ` Christopher J. PeBenito
2012-12-17 9:42 ` [refpolicy] [PATCH 4/8] Update towards apache_manage_all_content Sven Vermeulen
2013-01-03 15:13 ` Christopher J. PeBenito
2013-01-03 16:12 ` Sven Vermeulen
2013-01-03 16:24 ` Christopher J. PeBenito
2013-01-03 16:27 ` Christopher J. PeBenito
2013-01-11 18:29 ` Dominick Grift
2013-01-11 19:23 ` Sven Vermeulen
2012-12-17 9:42 ` [refpolicy] [PATCH 5/8] Dontaudit getsched on all domains Sven Vermeulen
2012-12-17 10:20 ` grift
2012-12-17 10:26 ` Sven Vermeulen
2012-12-21 20:17 ` Sven Vermeulen [this message]
2013-01-03 15:05 ` Christopher J. PeBenito
2012-12-17 9:42 ` [refpolicy] [PATCH 6/8] Allow initrc_t to read stunnel configuration Sven Vermeulen
2013-01-03 15:31 ` Christopher J. PeBenito
2012-12-17 9:42 ` [refpolicy] [PATCH 7/8] Introduce rw_inherited_file_perms definition Sven Vermeulen
2013-01-03 15:08 ` Christopher J. PeBenito
2012-12-17 9:42 ` [refpolicy] [PATCH 8/8] Introduce exec-check interfaces for passwd binaries and useradd binaries Sven Vermeulen
2013-01-03 15:31 ` Christopher J. 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=20121221201739.GA6960@siphos.be \
--to=sven.vermeulen@siphos.be \
--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.