netdev
[Top] [All Lists]

Re: [RFC][PATCH 2/3] netlink check sender, audit

To: Pablo Neira <pablo@xxxxxxxxxxx>
Subject: Re: [RFC][PATCH 2/3] netlink check sender, audit
From: Chris Wright <chrisw@xxxxxxxx>
Date: Tue, 15 Feb 2005 16:11:20 -0800
Cc: Chris Wright <chrisw@xxxxxxxx>, netdev@xxxxxxxxxxx, davem@xxxxxxxxxxxxx, jmorris@xxxxxxxxxx, sds@xxxxxxxxxxxxxx, serue@xxxxxxxxxx
In-reply-to: <42127764.5050507@xxxxxxxxxxx>
References: <20050212010243.W24171@xxxxxxxxxxxxxxxxxx> <20050212010504.X24171@xxxxxxxxxxxxxxxxxx> <420E334B.8060805@xxxxxxxxxxx> <420E77FA.6080007@xxxxxxxxxxx> <20050215001334.GB27645@xxxxxxxxxxxxxxxxxxx> <42115E7E.6050909@xxxxxxxxxxx> <20050215034708.GG27645@xxxxxxxxxxxxxxxxxxx> <4212757D.5070401@xxxxxxxxxxx> <20050215222246.GI15867@xxxxxxxxxxxxxxxxxxx> <42127764.5050507@xxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.6i
* Pablo Neira (pablo@xxxxxxxxxxx) wrote:
> I was aware of that. Actually I think that we can modify all calls to 
> netlink_kernel_create (that aren't that much) to fit the new interface, 
> I can post a patch to do that. I prefer providing just one function to 
> create a netlink socket in kernel space.

My only thought is as an exported symobl it's harder to be clear on
who's using it (possibly out-of-tree).

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

<Prev in Thread] Current Thread [Next in Thread>