All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Walters <walters@verbum.org>
To: Daniel J Walsh <Dan-Walsh@comcast.net>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>, SELinux <SELinux@tycho.nsa.gov>
Subject: Re: Category Translation patch for MCS/MLS Policy
Date: Mon, 08 Aug 2005 14:17:07 -0400	[thread overview]
Message-ID: <1123525027.636.9.camel@nexus.verbum.private> (raw)
In-Reply-To: <42F38DA8.4090300@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 554 bytes --]

On Fri, 2005-08-05 at 12:02 -0400, Daniel J Walsh wrote:
> I have written up a patch for libselinux to implement two functions, to 
> translate the security level.

To namespace these a bit more strongly (and make them easier to read),
perhaps something like:

> getselevelbyname

selinux_get_level_by_name

> getselevelbysename

selinux_get_level_by_sename  (there may be a better name here, not sure)

> setransconlevel

selinux_translate_level

> typedef struct selevel {

Perhaps struct selinux_category/selinux_category_t?



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-08-08 18:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05 16:02 Category Translation patch for MCS/MLS Policy Daniel J Walsh
2005-08-08 17:43 ` Casey Schaufler
2005-08-08 19:33   ` Joshua Brindle
2005-08-08 17:56 ` Darrel Goeddel
2005-08-08 18:02   ` Darrel Goeddel
2005-08-10 11:30     ` Daniel J Walsh
2005-08-10 12:02       ` Stephen Smalley
2005-08-10 15:11       ` Casey Schaufler
2005-08-08 18:17 ` Colin Walters [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-15 20:35 Chad Hanson
2005-08-16 12:56 ` 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=1123525027.636.9.camel@nexus.verbum.private \
    --to=walters@verbum.org \
    --cc=Dan-Walsh@comcast.net \
    --cc=SELinux@tycho.nsa.gov \
    --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.