From: Patrick McHardy <kaber@trash.net>
To: James Morris <jmorris@namei.org>
Cc: selinux@tycho.nsa.gov, netdev@vger.kernel.org,
netfilter-devel@lists.netfilter.org,
Stephen Smalley <sds@tycho.nsa.gov>,
Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: [RFC][SECMARK 03/08] Add xtables SECMARK target
Date: Thu, 11 May 2006 09:06:41 +0200 [thread overview]
Message-ID: <4462E281.7000400@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0605100925340.30577@d.namei>
James Morris wrote:
> On Wed, 10 May 2006, Patrick McHardy wrote:
>
>
>>The netfilter parts all look fine too me (just one question,
>>see below). Shall I add the userspace parts to SVN or do you
>>want to do it yourself?
>
>
> Might be better if you do it, although I'm still looking into one issue at
> this stage.
Just tell me when you want me to add it.
next prev parent reply other threads:[~2006-05-11 7:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 15:31 [RFC] SECMARK 1.0 James Morris
2006-05-07 15:33 ` [RFC] [SECMARK 01/08] Add secmark support to core networking James Morris
2006-05-07 15:34 ` [RFC][SECMARK 02/08] Export selinux_string_to_sid from SELinux James Morris
2006-05-07 15:35 ` [RFC][SECMARK 03/08] Add xtables SECMARK target James Morris
2006-05-10 6:03 ` Patrick McHardy
2006-05-10 13:30 ` James Morris
2006-05-11 7:06 ` Patrick McHardy [this message]
2006-05-07 15:36 ` [RFC][SECMARK 04/08] Add new flask definitions to SELinux James Morris
2006-05-07 15:37 ` [RFC][SECMARK 05/08] Add new packet controls " James Morris
2006-05-07 15:38 ` [RFC][SECMARK 06/08] Define a relabelto permission in the SELinux packet class James Morris
2006-05-07 15:39 ` [RFC][SECMARK 07/08] Add selinux_relabel_packet_permission() to SELinux API James Morris
2006-05-07 15:40 ` [RFC][SECMARK 08/08] Add selinux_relabel_packet_permission() check to xt_SECMARK James Morris
2006-05-08 17:54 ` Karl MacMillan
2006-05-08 21:19 ` James Morris
2006-05-07 15:42 ` [RFC][SECMARK userland 01/03] Add libselinux support James Morris
2006-05-07 15:43 ` [RFC][SECMARK userland 02/03] Add libipt_SECMARK James Morris
2006-05-07 15:44 ` [RFC][SECMARK userland 03/03] Add libip6t_SECMARK James Morris
2006-05-07 17:04 ` [RFC] SECMARK 1.0 Joshua Brindle
2006-05-07 17:43 ` James Morris
2006-05-08 17:41 ` Karl MacMillan
2006-05-08 21:29 ` James Morris
2006-05-09 13:24 ` Karl MacMillan
2006-05-09 16:40 ` James Morris
2006-05-09 17:06 ` Karl MacMillan
2006-05-09 18:56 ` James Morris
2006-05-09 17:11 ` Stephen Smalley
2006-05-07 17:44 ` James Morris
2006-05-14 6:03 ` [RFC] SECMARK 1.1 James Morris
2006-05-14 18:37 ` Patrick McHardy
2006-05-15 4:24 ` James Morris
2006-05-15 5:29 ` Patrick McHardy
2006-05-15 5:57 ` James Morris
2006-05-15 6:04 ` Patrick McHardy
2006-05-15 6:22 ` James Morris
2006-05-15 6:26 ` Patrick McHardy
2006-05-15 6:37 ` James Morris
2006-05-15 6:42 ` James Morris
2006-05-15 6:43 ` Patrick McHardy
2006-05-15 12:35 ` Karl MacMillan
2006-05-17 13:36 ` Thomas Bleher
2006-05-17 14:56 ` James Morris
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=4462E281.7000400@trash.net \
--to=kaber@trash.net \
--cc=dwalsh@redhat.com \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).