From: Richard Haines <richard_c_haines@btinternet.com>
To: SELinux List <selinux@tycho.nsa.gov>
Subject: Problem building CIL module with new class
Date: Thu, 17 Mar 2016 15:25:15 +0000 (UTC) [thread overview]
Message-ID: <1198187673.578619.1458228315066.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: 1198187673.578619.1458228315066.JavaMail.yahoo.ref@mail.yahoo.com
Using Fedora 23 targeted policy.
Problem: When adding a new class via the CIL module listed below, the allow
rule is not being resolved if the new class references a common set of
permissions.
Viewing with apol shows that the new class has been allocated the unique and
common permissions, however the allow rule is missing.
Note 1: If the 'all' expression is replaced in the 'classpermissionset' with
the actual permissions, then the allow rule is resolved.
Note 2: If I use the latest 2.5 libsepol with the
(classorder (unordered sctp_socket)) statement I get the same result.
The example CIL policy module is:
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
(classorder (proxy sctp_socket)) ; 'proxy' is the last class defined in F-23
; and required when using libsepol 2.4
(classcommon sctp_socket socket)
(class sctp_socket (node_bind name_connect association bindx_add bindx_rem
connectx peeloff set_addr set_params))
(classpermission sctp_socket_all_perms)
(classpermissionset sctp_socket_all_perms (sctp_socket (all)))
(allow unconfined_t self sctp_socket_all_perms)
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
And is built with the following command:
semodule --priority 400 -i sctp_test_module.cil
Any ideas !!!
Richard
next parent reply other threads:[~2016-03-17 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1198187673.578619.1458228315066.JavaMail.yahoo.ref@mail.yahoo.com>
2016-03-17 15:25 ` Richard Haines [this message]
2016-03-17 15:56 ` Problem building CIL module with new class Dominick Grift
2016-03-17 16:04 ` Dominick Grift
2016-03-17 17:20 ` Steve Lawrence
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=1198187673.578619.1458228315066.JavaMail.yahoo@mail.yahoo.com \
--to=richard_c_haines@btinternet.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.