From: Shaun Savage <savages@pcez.com>
To: SELinux@tycho.nsa.gov
Subject: Re: iptables.te errors
Date: Mon, 17 Dec 2001 08:41:21 -0800 [thread overview]
Message-ID: <3C1E2031.4030106@pcez.com> (raw)
In-Reply-To: Pine.GSO.4.33.0112170754050.10438-100000@raven
>
>
>>I have a iptables.te with some documentation.
>>
>
>Thanks for contributing. However, I was wondering if the additional
>permissions that you've defined should be merged back into the ipchains_t
>domain, and that domain could be used for both programs. Is there any
>real reason to maintain separate domains for the two programs?
>
>
I wanted try a simple example of a new policy. I wanted to try to find
all the hooks in other te's that needed to be added.
It was a learning process, and I hope to help selinux.
I have a K-12 school district that wants a secure base platform. I hope
to create a educational=RH+selinux-(most).
Shaun savage
--
You have received this message because you are subscribed to the selinux 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 prev parent reply other threads:[~2001-12-17 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 18:06 iptables.te errors Shaun Savage
2001-12-17 2:18 ` Paul Krumviede
2001-12-17 5:48 ` Shaun Savage
2001-12-17 12:55 ` Stephen Smalley
2001-12-17 16:41 ` Shaun Savage [this message]
2001-12-17 12:42 ` Stephen Smalley
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=3C1E2031.4030106@pcez.com \
--to=savages@pcez.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.