All of lore.kernel.org
 help / color / mirror / Atom feed
From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH/RFC 15/19]: patch set to update the git reference policy
Date: Mon, 24 Jan 2011 21:54:16 +0100	[thread overview]
Message-ID: <1295902456.31686.17.camel@tesla.lan> (raw)
In-Reply-To: <4D3D8545.30607@gmail.com>

On Mon, 24/01/2011 at 14.57 +0100, Dominick Grift wrote:
> On 01/24/2011 01:44 AM, Guido Trentalancia wrote:
> > diff -pruN -x .git -x booleans.conf -x corenetwork.if -x corenetwork.te -x modules.conf refpolicy-git-18012011/policy/modules/system/selinuxutil.te refpolicy-git-18012011-new/policy/modules/system/selinuxutil.te
> > --- refpolicy-git-18012011/policy/modules/system/selinuxutil.te	2011-01-17 19:36:10.814131755 +0100
> > +++ refpolicy-git-18012011-new/policy/modules/system/selinuxutil.te	2011-01-23 04:14:02.662963912 +0100
> > @@ -444,6 +444,7 @@ files_read_etc_files(semanage_t)
> >  files_read_etc_runtime_files(semanage_t)
> >  files_read_usr_files(semanage_t)
> >  files_list_pids(semanage_t)
> > +files_search_default(semanage_t)
> 
> There should not be any default_t directories. Thus this shouldnt be
> allowed.

This stems from the fact that at some point I came to a state where
while working from the terminal (as opposed to working from a graphical
terminal), semanage had trouble dealing with some temporary local
modules that I was working with for testing purposes (they were labelled
default_t)...

Of course it can be removed. So, in general default_t should never
appear anywhere in the policy ? Just for curiosity, what is the reason
behind that ? If it is allowed to carry out operations on usr and
etc_runtime files, why shouldn't it allowed to carry out operations on
default_t ?

Regards,

Guido

  reply	other threads:[~2011-01-24 20:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24  0:44 [refpolicy] [PATCH/RFC 15/19]: patch set to update the git reference policy Guido Trentalancia
2011-01-24 13:57 ` Dominick Grift
2011-01-24 20:54   ` Guido Trentalancia [this message]
2011-01-24 21:01     ` Dominick Grift
     [not found]       ` <4D470FB3.3080507@tresys.com>
2011-01-31 22:46         ` Guido Trentalancia

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=1295902456.31686.17.camel@tesla.lan \
    --to=guido@trentalancia.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.