From: Daniel J Walsh <dwalsh@redhat.com>
To: Chad Hanson <chanson@TrustedCS.com>
Cc: "SE Linux (E-mail)" <SELinux@tycho.nsa.gov>,
"Stephen Smalley (E-mail)" <sds@epoch.ncsc.mil>,
Darrel Goeddel <DGoeddel@TrustedCS.com>
Subject: Re: [PATCH] libsetrans
Date: Tue, 25 Oct 2005 17:14:30 -0400 [thread overview]
Message-ID: <435EA036.7000707@redhat.com> (raw)
In-Reply-To: <36282A1733C57546BE392885C0618592D3A092@chaos.tcs.tcs-sec.com>
Chad Hanson wrote:
> The following proposed patch to libsetrans incorporates the following
> changes:
>
> - Make libsetrans generic by creating a setrans config file
> - Add translation config file for MLS policy
> - Fix to handle translation for same level range string without separate
> definition (e.g. SystemHigh-SystemHigh)
> - move libsetrans disable option from translation config file
> (mcs.conf/mls.conf) to setrans config file
> - Some comment updates for mcs.conf
>
> -Chad
>
>
How about instead of adding another config file, we default the file to
the current policy that is installed.
/etc/selinux/setrans_mls.conf and /etc/selinux/setrans_targeted.conf
libselinux already reads config file so this will require no additional
perms, or we just put them into the policy file.
/etc/selinux/TYPE/setrans.conf
--
--
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 prev parent reply other threads:[~2005-10-25 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 20:55 [PATCH] libsetrans Chad Hanson
2005-10-25 21:14 ` Daniel J Walsh [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-25 23:12 Chad Hanson
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=435EA036.7000707@redhat.com \
--to=dwalsh@redhat.com \
--cc=DGoeddel@TrustedCS.com \
--cc=SELinux@tycho.nsa.gov \
--cc=chanson@TrustedCS.com \
--cc=sds@epoch.ncsc.mil \
/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.