netdev - Re: [PATCH net-2.6.26] netlink: make socket filters work on netlink

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 01 Apr 2008 13:52:49 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	hadi@...erus.ca
CC:	David Miller <davem@...emloft.net>, shemminger@...tta.com,
	netdev@...r.kernel.org
Subject: Re: [PATCH net-2.6.26] netlink: make socket filters work on netlink

jamal wrote:
> On Mon, 2008-31-03 at 22:15 +0200, Patrick McHardy wrote:
> 
>> I'll cook something up based on my and Stephen's patches.
> 
> Nice - now we can move all the filtering off iproute2;->
> 
> My view is that the nature of most stuff to filter on _events_ will
> depend on something along a "whodunnit" field. Route messages have a
> rudimentary form of such a field (the "protocol" field on the quagga
> patch Stephen posted for example uses it). It would be really nice to be
> able to generate such a field on all events to emit say the processid of
> the process which caused the event. Ive been thinking of adding a
> permanent field like that on the actions/filters. What are peoples
> thoughts on that?


Isn't that what nlmsg_pid already contains?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html