All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: "Gienek Nowacki" <nowackig@gmail.com>
Cc: <selinux@tycho.nsa.gov>
Subject: Re: Problem with corenet_* statements.
Date: Tue, 4 Mar 2008 08:49:23 -0500	[thread overview]
Message-ID: <1204638563.14217.8.camel@gorn> (raw)
In-Reply-To: <29e7ef020803031339h759da5f9gd0eb196eb638ac6b@mail.gmail.com>

On Mon, 2008-03-03 at 22:39 +0100, Gienek Nowacki wrote:
> Hi,
> 
> I would like to build my own SE module. The system is CentOS 5.1. The
> source of the module is as follow:
> 
> # ============ amav.te ===================
> 
> module amav 1.0.0;
> require {
>         type amavis_t;
> };
> corenet_udp_bind_generic_port(amavis_t);
> corenet_dontaudit_udp_bind_all_ports(amavis_t);
> 
> # ====================================
> 
> After running the command:
> checkmodule -M -m -o amav.mod  amav.te
> 
> ....there is `syntax error' -  checkmodule doasn't recognize
> corenet_*  statements.
> 
> Next, after successful I would like to use semodule_package and
> semodule commands.

If you use reference policy interfaces, you must use the reference
policy build infrastructure to process it.  Run

make -f /usr/share/selinux/devel/Makefile

and that will compile and package the module, so you'll get the amav.pp.

-- 
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150



--
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-03-04 14:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03 21:39 Problem with corenet_* statements Gienek Nowacki
2008-03-04 13:49 ` Christopher J. PeBenito [this message]
2008-03-04 14:09 ` Daniel J Walsh

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=1204638563.14217.8.camel@gorn \
    --to=cpebenito@tresys.com \
    --cc=nowackig@gmail.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.