From: David Miller <davem@davemloft.net>
To: torvalds@linux-foundation.org
Cc: drosenberg@vsecurity.com, chas@cmf.nrl.navy.mil,
kuznet@ms2.inr.ac.ru, pekkas@netcore.fi, jmorris@namei.org,
yoshfuji@linux-ipv6.org, kaber@trash.net,
remi.denis-courmont@nokia.com, netdev@vger.kernel.org,
security@kernel.org
Subject: Re: [Security] [SECURITY] Fix leaking of kernel heap addresses via /proc
Date: Sat, 06 Nov 2010 16:57:03 -0700 (PDT) [thread overview]
Message-ID: <20101106.165703.193714684.davem@davemloft.net> (raw)
In-Reply-To: <AANLkTimC01SViEOObgf2N2VcLTYO59rOAbHaKf2RM54w@mail.gmail.com>
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat, 6 Nov 2010 13:50:32 -0700
> On Saturday, November 6, 2010, Dan Rosenberg <drosenberg@vsecurity.com> wrote:
>>
>> Clearly, in most cases we cannot just remove the field from the /proc
>> output, as this would break a number of userspace programs that rely on
>> consistency. However, I propose that we replace the address with a "0"
>> rather than leaking this information.
>
> I really think it would be much better to use the unidentified number
> or similar.
>
> Just replacing with zeroes is annoying, and has the potential of
> losing actual information.
I would really like to see the specific examples of where this is
happening, it sounds like something very silly to me.
next prev parent reply other threads:[~2010-11-06 23:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 20:11 [SECURITY] Fix leaking of kernel heap addresses via /proc Dan Rosenberg
2010-11-06 20:50 ` [Security] " Linus Torvalds
2010-11-06 23:48 ` Ted Ts'o
2010-11-07 21:52 ` Andi Kleen
2010-11-07 22:48 ` Chas Williams (CONTRACTOR)
2010-11-07 23:14 ` Andi Kleen
2010-11-07 23:22 ` Linus Torvalds
2010-11-07 23:29 ` Andi Kleen
2010-11-07 23:27 ` Dan Rosenberg
2010-11-07 23:56 ` Andi Kleen
2010-11-08 2:01 ` David Miller
2010-11-08 7:33 ` Eric Dumazet
2010-11-08 9:43 ` Andi Kleen
2010-11-08 10:14 ` Eric Dumazet
2010-11-06 23:57 ` David Miller [this message]
2010-11-07 10:28 ` Oliver Hartkopp
2010-11-07 17:11 ` Ben Hutchings
2010-11-08 1:00 ` Willy Tarreau
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=20101106.165703.193714684.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=chas@cmf.nrl.navy.mil \
--cc=drosenberg@vsecurity.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=pekkas@netcore.fi \
--cc=remi.denis-courmont@nokia.com \
--cc=security@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).