From: Steve Lawrence <slawrence@tresys.com>
To: Dan <dtdevore64@yahoo.com>, <selinux@tycho.nsa.gov>
Subject: Re: Trouble building a .cil policy from scratch.
Date: Thu, 23 Jul 2015 07:42:46 -0400 [thread overview]
Message-ID: <55B0D336.1010406@tresys.com> (raw)
In-Reply-To: <55B01776.3030308@yahoo.com>
On 07/22/2015 06:21 PM, Dan wrote:
> Hey guys, I've been reading the documentation of CIL language and have
> been practicing writing policies from scratch and have come across a
> problem. Here is what I have so far(which is just a simple example):
>
> (type myapp_t)
> (role object_r)
> (role staff_r)
> (roletype object_r myapp_t)
> (typeattribute domain)
> (typeattributetypes domain (myapp_t))
>
>
> (type myapp_exec_t)
> (roletype object_r myapp_exec_t)
> (typeattribute domain)
> (typeattributetypes domain (myapp_exec_t))
>
>
>
> Now I know I need other stuff to build this module completely like SID,
> access vectors, etc, but I'm stuck because it doesn't recognize the
> "typeattributetypes" statement. It just spits out the error as an
> unknown keyword which I don't know why I would because I'm pretty sure I
> used it right, but I'm still learning. Any info would be awesome. Thanks
> guys.
>
typeattributetypes is an old statement that no longer exists. It was
renamed to typeattributeset. The CIL documentation on the wiki is pretty
out of date. I'd recommend just looking at the docs in the secilc
directory in the selinux userspace repo. Running make in secilc/docs
will create an html and pdf version of the documentation, which should
be pretty up to date.
next prev parent reply other threads:[~2015-07-23 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 22:21 Trouble building a .cil policy from scratch Dan
2015-07-23 11:42 ` Steve Lawrence [this message]
2015-07-23 18:27 ` Dan
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=55B0D336.1010406@tresys.com \
--to=slawrence@tresys.com \
--cc=dtdevore64@yahoo.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.