All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: "Eric Paris" <eparis@parisplace.org>
Cc: selinux <selinux@tycho.nsa.gov>
Subject: Re: [PATCH 0/5] New labeled networking permissions for 2.6.25
Date: Tue, 26 Feb 2008 17:08:08 -0500	[thread overview]
Message-ID: <200802261708.08090.paul.moore@hp.com> (raw)
In-Reply-To: <7e0fb38c0802261352r52318774v562f8e635a3f44cc@mail.gmail.com>

On Tuesday 26 February 2008 4:52:34 pm Eric Paris wrote:
> On 2/26/08, paul.moore@hp.com <paul.moore@hp.com> wrote:
> >  It is important to note that
> >  while this patchset adds the permissions required it doesn't
> > enable the "network_peer_controls" policy capability.
>
> Darn it, I'm trying to play with a new capability for something I'm
> writing and I just read this whole patch set (before i read 0/5) to
> see where you decided to define it so I could copy that in my policy.
> Thanks for not doing the one thing I was hunting for!

Well, thanks for looking at the code ;)

I currently enable the functionality with a simple module which consists 
solely of the lines below:

 policy_module(peer_test,0.0.2)
 policycap network_peer_controls;
 # dummy type - not used
 type peer_test_t;

However, be warned that the policy toolchain in rawhide won't compile 
this correctly at present (well, as of this morning anyway) so you have 
to get the bits from SVN.  This is one of the reasons why I didn't 
submit a patch enabling the policy capabilities (that and there needs 
to be more testing done first).

> So, does anyone have a good idea suggestions where we should turn
> on/off these new capabilities?  I know it has to be in the base
> module in the end, but I don't know what file to put them in.  I
> might just throw it in kernel.te for now for me to keep testing but I
> assume we are going to want all of these definitions in one place? 
> Are we going to want them all over as long as they end up being built
> into base?

I have no idea but I suspect Chris has given this some thought and 
probably has some ideas.  I tend to think putting them in one place is 
probably a good idea ...

-- 
paul moore
linux security @ hp

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2008-02-26 22:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 18:40 [PATCH 0/5] New labeled networking permissions for 2.6.25 paul.moore
2008-02-26 18:40 ` [PATCH 1/5] REFPOL: Add new labeled networking permissions paul.moore
2008-03-19 13:19   ` Christopher J. PeBenito
2008-03-19 18:24     ` Paul Moore
2008-03-20 12:50       ` Christopher J. PeBenito
2008-03-20 15:08         ` Paul Moore
2008-02-26 18:40 ` [PATCH 2/5] REFPOL: Allow network admin domains to receive unlabeled traffic paul.moore
2008-02-26 18:40 ` [PATCH 3/5] REFPOL: Allow network apps " paul.moore
2008-02-26 18:40 ` [PATCH 4/5] REFPOL: Allow network service " paul.moore
2008-02-26 18:40 ` [PATCH 5/5] REFPOL: Allow network system " paul.moore
2008-02-26 21:52 ` [PATCH 0/5] New labeled networking permissions for 2.6.25 Eric Paris
2008-02-26 22:08   ` Paul Moore [this message]
2008-02-27 13:23     ` Christopher J. PeBenito
2008-02-27 14:35       ` Paul Moore

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=200802261708.08090.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=eparis@parisplace.org \
    --cc=selinux@tycho.nsa.gov \
    /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.