From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: kees.cook@canonical.com, joe@perches.com, mingo@elte.hu,
akpm@linux-foundation.org, netdev@vger.kernel.org,
drosenberg@vsecurity.com, a.p.zijlstra@chello.nl,
eparis@parisplace.org, eugeneteo@kernel.org, jmorris@namei.org,
tgraf@infradead.org
Subject: Re: [patch 1/1] net: convert %p usage to %pK
Date: Fri, 27 May 2011 05:10:41 +0200 [thread overview]
Message-ID: <1306465841.2543.52.camel@edumazet-laptop> (raw)
In-Reply-To: <20110526.224427.433160775431725543.davem@davemloft.net>
Le jeudi 26 mai 2011 à 22:44 -0400, David Miller a écrit :
> From: Kees Cook <kees.cook@canonical.com>
> Date: Thu, 26 May 2011 17:14:49 -0700
> >
> > 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)
next prev parent reply other threads:[~2011-05-27 3:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 22:17 [patch 1/1] net: convert %p usage to %pK akpm
2011-05-24 5:13 ` David Miller
2011-05-24 6:17 ` Eric Dumazet
2011-05-24 6:33 ` Joe Perches
2011-05-24 6:57 ` Ingo Molnar
2011-05-24 7:04 ` Eric Dumazet
2011-05-24 7:35 ` Joe Perches
2011-05-24 7:45 ` Eric Dumazet
2011-05-24 7:58 ` David Miller
2011-05-24 14:43 ` Stephen Hemminger
2011-05-24 17:18 ` David Miller
2011-05-25 23:29 ` Kees Cook
2011-05-26 1:50 ` David Miller
2011-05-27 0:14 ` Kees Cook
2011-05-27 2:44 ` David Miller
2011-05-27 3:10 ` Eric Dumazet [this message]
2011-05-27 6:37 ` Ingo Molnar
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=1306465841.2543.52.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=drosenberg@vsecurity.com \
--cc=eparis@parisplace.org \
--cc=eugeneteo@kernel.org \
--cc=jmorris@namei.org \
--cc=joe@perches.com \
--cc=kees.cook@canonical.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=tgraf@infradead.org \
/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