[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1285605845.2815.7.camel@localhost.localdomain>
Date: Mon, 27 Sep 2010 12:44:05 -0400
From: Eric Paris <eparis@...hat.com>
To: Pablo Neira Ayuso <pablo@...filter.org>
Cc: linux-kernel@...r.kernel.org, selinux@...ho.nsa.gov,
netfilter-devel@...r.kernel.org, jmorris@...ei.org,
sds@...ho.nsa.gov, jengelh@...ozas.de, paul.moore@...com,
casey@...aufler-ca.com, linux-security-module@...r.kernel.org,
netfilter@...r.kernel.org, mr.dash.four@...glemail.com
Subject: Re: [PATCH 3/6] secmark: export binary yes/no rather than kernel
internal secid
On Sat, 2010-09-25 at 10:41 +0200, Pablo Neira Ayuso wrote:
> On 24/09/10 22:45, Eric Paris wrote:
> > Currently the nfconntrack export code sends the kernel internal secid to
> > userspace in a couple of proc files and over netlink as an integer. This
> > is wrong. This number is a kernel internal. This patch changes the export
> > code to output either 0 or 1 for this value. A future patch will implement
> > sending the name rather than the number in a new field.
>
> I'm not sure why you need this transitional patch if you later on
> replace it.
>
> Better to change the /proc output to make it consistent with patch 5/6?
Jan has stated his opinion I should not export the new secctx field via
the procfs interface. This patch was included in the series in case
that was the consensus of the lists and thus we just wouldn't apply
patch 6/6 (which drops secmark and adds secctx to procfs)
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists