All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <jbrindle@tresys.com>
To: dccp@vger.kernel.org
Subject: Re: [PATCH RFC] SELinux support for DCCP
Date: Sat, 11 Nov 2006 15:56:33 +0000	[thread overview]
Message-ID: <4555F2B1.6050003@tresys.com> (raw)
In-Reply-To: <XMMS.LNX.4.64.0611110203540.25507@d.namei>

James Morris wrote:
> The kernel patch is included below, please review.
>
> Signed-off-by: James Morris <jmorris@namei.org>
>   
> +#define CONTEXT__TRANSLATE                        0x00000001UL
> +#define CONTEXT__CONTAINS                         0x00000002UL
>   
> +   S_(SECCLASS_CONTEXT, CONTEXT__TRANSLATE, "translate")
> +   S_(SECCLASS_CONTEXT, CONTEXT__CONTAINS, "contains")
>   
> +    S_("context")
>   
> +#define SECCLASS_CONTEXT                                 59
>   

oops?


WARNING: multiple messages have this Message-ID (diff)
From: Joshua Brindle <jbrindle@tresys.com>
To: James Morris <jmorris@namei.org>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	dccp@vger.kernel.org, selinux@tycho.nsa.gov
Subject: Re: [PATCH RFC] SELinux support for DCCP
Date: Sat, 11 Nov 2006 10:56:33 -0500	[thread overview]
Message-ID: <4555F2B1.6050003@tresys.com> (raw)
In-Reply-To: <XMMS.LNX.4.64.0611110203540.25507@d.namei>

James Morris wrote:
> The kernel patch is included below, please review.
>
> Signed-off-by: James Morris <jmorris@namei.org>
>   
> +#define CONTEXT__TRANSLATE                        0x00000001UL
> +#define CONTEXT__CONTAINS                         0x00000002UL
>   
> +   S_(SECCLASS_CONTEXT, CONTEXT__TRANSLATE, "translate")
> +   S_(SECCLASS_CONTEXT, CONTEXT__CONTAINS, "contains")
>   
> +    S_("context")
>   
> +#define SECCLASS_CONTEXT                                 59
>   

oops?


--
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.

  parent reply	other threads:[~2006-11-11 15:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11  7:16 [PATCH RFC] SELinux support for DCCP James Morris
2006-11-11  7:16 ` James Morris
2006-11-11 15:46 ` Eric Paris
2006-11-11 15:46   ` Eric Paris
2006-11-11 15:56 ` Joshua Brindle [this message]
2006-11-11 15:56   ` Joshua Brindle
2006-11-11 17:46 ` James Morris
2006-11-11 17:46   ` James Morris
2006-11-11 17:47 ` James Morris
2006-11-11 17:47   ` James Morris
2006-11-11 17:49 ` Joshua Brindle
2006-11-11 17:49   ` Joshua Brindle
2006-11-11 18:03 ` James Morris
2006-11-11 18:03   ` James Morris
2006-11-13 13:28   ` Flask headers (Was: RE: [PATCH RFC] SELinux support for DCCP) Stephen Smalley
2006-11-13 16:30     ` Christopher J. PeBenito
2006-11-13 16:38       ` Stephen Smalley
2006-11-13 16:43         ` James Morris
2006-11-11 18:11 ` [PATCH RFC] SELinux support for DCCP James Morris
2006-11-11 18:11   ` James Morris
2006-11-11 18:22 ` Joshua Brindle
2006-11-11 18:22   ` Joshua Brindle
2006-11-12  0:36 ` Arnaldo Carvalho de Melo
2006-11-13 20:44 ` Paul Moore
2006-11-13 20:44   ` Paul Moore
2006-11-13 20:54 ` Paul Moore
2006-11-13 20:54   ` Paul Moore
2006-11-13 21:18 ` James Morris
2006-11-13 21:18   ` James Morris
2006-11-29 22:57 ` Gerrit Renker

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=4555F2B1.6050003@tresys.com \
    --to=jbrindle@tresys.com \
    --cc=dccp@vger.kernel.org \
    /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.