From: Vasiliy Kulikov <segoon@openwall.com>
To: Guillaume Chazarain <guichaz@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Balbir Singh <bsingharora@gmail.com>,
kernel-hardening@lists.openwall.com
Subject: Re: taskstats root only breaking iotop
Date: Sun, 2 Oct 2011 14:54:57 +0400 [thread overview]
Message-ID: <20111002105457.GA5598@albatros> (raw)
In-Reply-To: <CAA879TMgMm4u6kDFahXqCHAFyvDc_hTt+Q93tdSdHKnAcUaMTw@mail.gmail.com>
(cc'ed kernel-hardening)
On Sun, Oct 02, 2011 at 12:22 +0200, Guillaume Chazarain wrote:
> On Sun, Oct 2, 2011 at 2:20 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> > So I don't see why you ask for it. What could possibly be a valid use-case?
>
> Right, kbyte granularity is enough.
It is not enough. In some border cases an attacker may still learn
private information given the counters with _arbitrary_ granularity:
http://www.openwall.com/lists/oss-security/2011/06/29/9
> And that's consistent with
> /proc/vmstat, which nobody is complaining about.
<jumping with a raised hand>Me, me, it was me!</jumping with a raised hand>
Seriously, most of procfs files were created with relaxed permissions in
old days when nobody thought about such infoleaks. Now it is much
harder to close all of them without breaking existing users.
http://www.openwall.com/lists/kernel-hardening/2011/07/28/1
http://www.openwall.com/lists/kernel-hardening/2011/09/27/3
http://www.openwall.com/lists/kernel-hardening/2011/09/19/24
http://www.openwall.com/lists/kernel-hardening/2011/09/21/2
Thanks,
--
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
next prev parent reply other threads:[~2011-10-02 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-01 21:54 taskstats root only breaking iotop Guillaume Chazarain
2011-10-01 21:59 ` Linus Torvalds
2011-10-01 22:41 ` Guillaume Chazarain
2011-10-02 0:20 ` Linus Torvalds
2011-10-02 10:22 ` Guillaume Chazarain
2011-10-02 10:54 ` Vasiliy Kulikov [this message]
2011-10-03 12:31 ` Adrian Bunk
2011-10-04 13:31 ` Vasiliy Kulikov
2011-10-03 14:52 ` Balbir Singh
2011-10-03 15:20 ` Linus Torvalds
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=20111002105457.GA5598@albatros \
--to=segoon@openwall.com \
--cc=bsingharora@gmail.com \
--cc=guichaz@gmail.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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