From: Paul Moore <paul.moore@hp.com>
To: selinux@tycho.nsa.gov
Subject: [PATCH] REFPOL: Add "rogue" Fedora packet class permissions
Date: Thu, 17 Jan 2008 12:22:42 -0500 [thread overview]
Message-ID: <20080117172246.341834342@hp.com> (raw)
At some point in the Fedora 6 timeframe the "flow_in" and "flow_out"
permissions were added to the "packet" class, most likely as part of the
ill-fated secid-reconciliation effort. Despite the fact that these permissions
are not currently used they should be included in the Reference Policy as they
are now a permanent fixture in Fedora and it is crucial that the FLASK
defines be kept in sync.
This patch needs to be applied before any other patches that affect the
"packet" class, otherwise the resulting policy may not load.
Signed-off-by: Paul Moore <paul.moore@hp.com>
---
policy/flask/access_vectors | 2 ++
1 file changed, 2 insertions(+)
Index: refpolicy_svn_repo/policy/flask/access_vectors
===================================================================
--- refpolicy_svn_repo.orig/policy/flask/access_vectors
+++ refpolicy_svn_repo/policy/flask/access_vectors
@@ -644,6 +644,8 @@ class packet
send
recv
relabelto
+ flow_in # not currently in use
+ flow_out # not currently in use
}
class key
--
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.
next reply other threads:[~2008-01-17 17:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 17:22 Paul Moore [this message]
2008-01-17 17:30 ` [PATCH] REFPOL: Add "rogue" Fedora packet class permissions Eric Paris
2008-01-17 19:13 ` Joshua Brindle
2008-01-17 19:23 ` Paul Moore
2008-01-17 19:33 ` Stephen Smalley
2008-01-18 13:32 ` Christopher J. PeBenito
2008-01-18 14:11 ` Paul Moore
2008-01-18 14:38 ` Christopher J. PeBenito
2008-01-19 3:44 ` Paul Moore
2008-01-18 15:06 ` Eric Paris
2008-01-18 16:52 ` Joshua Brindle
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=20080117172246.341834342@hp.com \
--to=paul.moore@hp.com \
--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.