From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dan Rosenberg <drosenberg@vsecurity.com>
Cc: "chas@cmf.nrl.navy.mil" <chas@cmf.nrl.navy.mil>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuznet@ms2.inr.ac.ru" <kuznet@ms2.inr.ac.ru>,
"pekkas@netcore.fi" <pekkas@netcore.fi>,
"jmorris@namei.org" <jmorris@namei.org>,
"yoshfuji@linux-ipv6.org" <yoshfuji@linux-ipv6.org>,
"kaber@trash.net" <kaber@trash.net>,
"remi.denis-courmont@nokia.com" <remi.denis-courmont@nokia.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"security@kernel.org" <security@kernel.org>
Subject: Re: [Security] [SECURITY] Fix leaking of kernel heap addresses via /proc
Date: Sat, 6 Nov 2010 13:50:32 -0700 [thread overview]
Message-ID: <AANLkTimC01SViEOObgf2N2VcLTYO59rOAbHaKf2RM54w@mail.gmail.com> (raw)
In-Reply-To: <1289074307.3090.100.camel@Dan>
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.
Linus
next prev parent reply other threads:[~2010-11-06 20:51 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 ` Linus Torvalds [this message]
2010-11-06 23:48 ` [Security] " 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
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=AANLkTimC01SViEOObgf2N2VcLTYO59rOAbHaKf2RM54w@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=chas@cmf.nrl.navy.mil \
--cc=davem@davemloft.net \
--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=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).