Le jeudi 26 mai 2011 à 22:44 -0400, David Miller a écrit :

From: Kees Cook <redacted>
Date: Thu, 26 May 2011 17:14:49 -0700

quoted

We got this dropped from the /proc view; why can't we do the same for
this netlink interface?

Because it's not only an opaque "output" blob, it's also an input key
for lookups which the user can trigger.

Yes, we wan add a layer to obfuscate the real pointers. We dont trust
values given by user, only match them.

Either we use a XOR with a boot time random value (but let the NULL
cookie being the NULL one), or we generate an unique 64bit socket id for
the cookie (and keep a 64bit cookie in all sockets, increasing ram
usage)