From: "Mikel L. Matthews" <mikel@argus-systems.com>
To: Paul Moore <paul.moore@hp.com>
Cc: James Morris <jmorris@namei.org>,
netdev@vger.kernel.org, linux-security-module@vger.kernel.org,
selinux@tycho.nsa.gov, James Morris <jmorris@redhat.com>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [RFC 0/4] NetLabel
Date: Fri, 26 May 2006 11:20:57 -0500 [thread overview]
Message-ID: <44772AE9.1060907@argus-systems.com> (raw)
In-Reply-To: <447729B7.4060702@hp.com>
Same issue, I would drop them.
Paul Moore wrote:
> Mikel L. Matthews wrote:
>> Paul Moore wrote:
>>> James Morris wrote:
>>
>
> Outgoing fragment *should* be labeled correctly assuming the Linux base
> network stack does the right thing (I haven't tested this yet). The
> issue we are discussing here is what to do about incoming packets where
> the fragments are not consistently labeled.
>
--
Thanks,
Mike
Mikel L. Matthews
Chief Technology Officer
Innovative Security Systems, Inc.
(dba Argus Systems Group)
1809 Woodfield Dr.
Savoy IL 61874
+1-217-355-6308
www.argus-systems.com
--
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.
WARNING: multiple messages have this Message-ID (diff)
From: "Mikel L. Matthews" <mikel@argus-systems.com>
To: Paul Moore <paul.moore@hp.com>
Cc: James Morris <jmorris@namei.org>,
netdev@vger.kernel.org, linux-security-module@vger.kernel.org,
selinux@tycho.nsa.gov, James Morris <jmorris@redhat.com>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [RFC 0/4] NetLabel
Date: Fri, 26 May 2006 11:20:57 -0500 [thread overview]
Message-ID: <44772AE9.1060907@argus-systems.com> (raw)
In-Reply-To: <447729B7.4060702@hp.com>
Same issue, I would drop them.
Paul Moore wrote:
> Mikel L. Matthews wrote:
>> Paul Moore wrote:
>>> James Morris wrote:
>>
>
> Outgoing fragment *should* be labeled correctly assuming the Linux base
> network stack does the right thing (I haven't tested this yet). The
> issue we are discussing here is what to do about incoming packets where
> the fragments are not consistently labeled.
>
--
Thanks,
Mike
Mikel L. Matthews
Chief Technology Officer
Innovative Security Systems, Inc.
(dba Argus Systems Group)
1809 Woodfield Dr.
Savoy IL 61874
+1-217-355-6308
www.argus-systems.com
next prev parent reply other threads:[~2006-05-26 16:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 20:06 [RFC 0/4] NetLabel Paul Moore
2006-05-25 20:06 ` Paul Moore
2006-05-25 20:58 ` Stephen Hemminger
2006-05-25 21:14 ` Paul Moore
2006-05-25 21:14 ` Paul Moore
2006-05-26 0:06 ` James Morris
2006-05-26 0:06 ` James Morris
2006-05-26 15:30 ` Paul Moore
2006-05-26 15:30 ` Paul Moore
2006-05-26 16:02 ` James Morris
2006-05-26 16:02 ` James Morris
2006-05-26 16:34 ` Paul Moore
2006-05-26 16:34 ` Paul Moore
2006-05-26 18:56 ` James Morris
2006-05-26 18:56 ` James Morris
2006-05-26 16:09 ` Mikel L. Matthews
2006-05-26 16:09 ` Mikel L. Matthews
2006-05-26 16:15 ` Paul Moore
2006-05-26 16:15 ` Paul Moore
2006-05-26 16:20 ` Mikel L. Matthews [this message]
2006-05-26 16:20 ` Mikel L. Matthews
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=44772AE9.1060907@argus-systems.com \
--to=mikel@argus-systems.com \
--cc=jmorris@namei.org \
--cc=jmorris@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.com \
--cc=sds@tycho.nsa.gov \
--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.