From: dominick.grift@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 04/20] seutils: restorecon wants to read /run symbolic link
Date: Thu, 26 Sep 2013 14:41:44 +0200 [thread overview]
Message-ID: <1380199304.2561.5.camel@d30> (raw)
In-Reply-To: <52442AD5.5020701@tresys.com>
On Thu, 2013-09-26 at 08:38 -0400, Christopher J. PeBenito wrote:
> On Tue 24 Sep 2013 09:39:16 AM EDT, Dominick Grift wrote:
> > Do not audit attempts by fixfiles to read all symbolic links
> >
> > Signed-off-by: Dominick Grift <dominick.grift@gmail.com>
> > ---
> > policy/modules/system/selinuxutil.te | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/policy/modules/system/selinuxutil.te b/policy/modules/system/selinuxutil.te
> > index 5622246..ff19d75 100644
> > --- a/policy/modules/system/selinuxutil.te
> > +++ b/policy/modules/system/selinuxutil.te
> > @@ -552,7 +552,7 @@ files_read_etc_runtime_files(setfiles_t)
> > files_read_etc_files(setfiles_t)
> > files_list_all(setfiles_t)
> > files_relabel_all_files(setfiles_t)
> > -files_read_usr_symlinks(setfiles_t)
> > +files_dontaudit_read_all_symlinks(setfiles_t)
> >
> > fs_getattr_xattr_fs(setfiles_t)
> > fs_list_all(setfiles_t)
>
> Can you further clarify this? Setfiles hasn't changed much in years,
> so I'm unclear on why this change is necessary.
This is not so much related to setfiles
its related to recent changes of locations. for example /var/run
-> /run, /bin -> /usr/bin etc.
So now /var/run is a symlink to /run.
setfiles doesnt follow symlinks so we might as well silently deny access
to read all symlinks
>
> --
> Chris PeBenito
> Tresys Technology, LLC
> www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2013-09-26 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 13:39 [refpolicy] [PATCH 04/20] seutils: restorecon wants to read /run symbolic link Dominick Grift
2013-09-26 12:38 ` Christopher J. PeBenito
2013-09-26 12:41 ` Dominick Grift [this message]
2013-09-27 20:58 ` Christopher J. PeBenito
2013-09-27 21:03 ` Dominick Grift
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=1380199304.2561.5.camel@d30 \
--to=dominick.grift@gmail.com \
--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.