All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linda Knippers <linda.knippers@hp.com>
To: James Morris <jmorris@namei.org>
Cc: Eric Paris <eparis@parisplace.org>,
	selinux@tycho.nsa.gov, redhat-lspp@redhat.com, paul.moore@hp.com,
	vyekkirala@TrustedCS.com
Subject: Re: RHEL5 Kernel with labeled networking
Date: Tue, 03 Oct 2006 12:24:10 -0400	[thread overview]
Message-ID: <45228EAA.5050105@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610031207260.21081@d.namei>

James Morris wrote:
> On Tue, 3 Oct 2006, Eric Paris wrote:
> 
> 
>>I think there is going to need to be a policy change that I'm actually
>>talking with Dan about as I type this e-mail.  I think we  need
>>
>>allow $1 unlabeled_t:packet { flow_in flow_out };
>>
>>to be added to policy to allow things to work as they did.  I'll post
>>again as soon as we have a policy that appears to let normal networking
>>work in enforcing.
> 
> 
> We need this policy in rawhide before the kernel patches are merged 
> upstream, so we can note the required policy version associated with the 
> patches.  We've do not want to kill Andrew Morton's box again with this 
> kind of thing.

Dumb question....should compat_net be "1" by default?

-- ljk

--
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:[~2006-10-03 16:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-03  0:23 RHEL5 Kernel with labeled networking Eric Paris
2006-10-03 15:34 ` Linda Knippers
2006-10-03 15:41   ` Stephen Smalley
2006-10-03 15:51     ` Linda Knippers
2006-10-03 16:12       ` Linda Knippers
2006-10-03 15:45   ` Eric Paris
2006-10-03 16:08     ` James Morris
2006-10-03 16:24       ` Linda Knippers [this message]
2006-10-03 16:41         ` James Morris
2006-10-03 16:46           ` Linda Knippers
2006-10-03 16:46       ` Joshua Brindle
2006-10-03 19:29         ` Joshua Brindle
2006-10-04 14:09       ` [redhat-lspp] " Stephen Smalley
2006-10-04 19:04       ` Daniel J Walsh
2006-10-03 16:40 ` Paul Moore
  -- strict thread matches above, loose matches on Subject: below --
2006-10-03 17:16 Venkat Yekkirala
2006-10-03 18:37 Joy Latten
2006-10-03 19:18 ` Joshua Brindle
2006-10-03 19:16   ` Joy Latten
2006-10-03 20:40     ` Linda Knippers
2006-10-03 21:25       ` Joshua Brindle
2006-10-03 21:27         ` Linda Knippers
2006-10-03 21:30           ` Karl MacMillan
2006-10-03 21:47             ` Linda Knippers
2006-10-03 22:40               ` Joshua Brindle
2006-10-03 22:59                 ` Linda Knippers
2006-10-04 14:57                   ` Stephen Smalley
2006-10-04 15:20                     ` Linda Knippers
2006-10-03 21:28         ` Karl MacMillan
2006-10-04 19:01 Joy Latten

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=45228EAA.5050105@hp.com \
    --to=linda.knippers@hp.com \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --cc=paul.moore@hp.com \
    --cc=redhat-lspp@redhat.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=vyekkirala@TrustedCS.com \
    /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.