From: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
To: James Morris <jmorris@namei.org>
Cc: Vasiliy Kulikov <segoon@openwall.com>,
kernel-hardening@lists.openwall.com,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [RFC 2/5 v4] procfs: add hidepid= and gid= mount options
Date: Mon, 20 Jun 2011 20:23:28 +0900 [thread overview]
Message-ID: <BANLkTi=vdCDnD-_Ut0si=dZ=zcDc_yiU0A@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1106202040400.10448@tundra.namei.org>
2011/6/20 James Morris <jmorris@namei.org>:
> On Mon, 20 Jun 2011, Vasiliy Kulikov wrote:
>
>> > Can you provide evidence that this is a useful feature? e.g. examples of
>> > exploits / techniques which would be _usefully_ hampered or blocked.
>>
>> First, most of these files are usefull in sense of statistics gathering
>> and debugging. There is no reason to provide this information to the
>> world.
>>
>> Second, yes, it blocks one source of information used in timing attacks,
>> just use reading the counters as more or less precise time measurement
>> when actual timing measurements are not precise enough.
>
> Can you provide concrete examples?
Vasiliy,
I'm now stand aside James. I mean, if we don't understand your usecase
clearly. we can't gurantee to don't break the feature in the future. So,
we strongly hope to understand it.
Moreover, _now_ I haven't understand your concrete usecase, and then
_I_ can't review and be convinced your code. Please please avoid one line
answer as far as possible, please provide us more information.
next prev parent reply other threads:[~2011-06-20 11:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LRH.2.00.1106192154220.7503@taiga.selinuxproject.org>
2011-06-20 5:07 ` [RFC 2/5 v4] procfs: add hidepid= and gid= mount options James Morris
2011-06-20 10:39 ` Vasiliy Kulikov
2011-06-20 10:43 ` James Morris
2011-06-20 11:23 ` KOSAKI Motohiro [this message]
2011-06-20 17:06 ` Vasiliy Kulikov
2011-06-20 19:41 ` Eric W. Biederman
2011-06-20 23:19 ` James Morris
2011-06-21 18:28 ` Vasiliy Kulikov
2011-06-20 13:58 ` Alexey Dobriyan
2011-06-20 13:31 ` Solar Designer
2011-06-15 18:51 Vasiliy Kulikov
2011-06-16 2:24 ` KOSAKI Motohiro
2011-06-16 8:47 ` Vasiliy Kulikov
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='BANLkTi=vdCDnD-_Ut0si=dZ=zcDc_yiU0A@mail.gmail.com' \
--to=kosaki.motohiro@gmail.com \
--cc=jmorris@namei.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=segoon@openwall.com \
/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).