From: Vasiliy Kulikov <segoon@openwall.com>
To: James Morris <jmorris@namei.org>
Cc: kernel-hardening@lists.openwall.com,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: [kernel-hardening] Re: [RFC 2/5 v4] procfs: add hidepid= and gid= mount options
Date: Tue, 21 Jun 2011 22:28:27 +0400 [thread overview]
Message-ID: <20110621182827.GA8960@albatros> (raw)
In-Reply-To: <alpine.LRH.2.00.1106202040400.10448@tundra.namei.org>
On Mon, Jun 20, 2011 at 20:43 +1000, James Morris wrote:
> 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?
This is a PoC of ~user/.ssh/authorized_keys presence infoleak (and
whether it is empty) using taskstats interface:
http://www.openwall.com/lists/oss-security/2011/06/21/12
/proc/PID/io can be used too.
More close interaction with ssh client would gain authorized_keys' size or,
probably, what pam module denied the access.
Thanks,
--
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
WARNING: multiple messages have this Message-ID (diff)
From: Vasiliy Kulikov <segoon@openwall.com>
To: James Morris <jmorris@namei.org>
Cc: 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: Tue, 21 Jun 2011 22:28:27 +0400 [thread overview]
Message-ID: <20110621182827.GA8960@albatros> (raw)
In-Reply-To: <alpine.LRH.2.00.1106202040400.10448@tundra.namei.org>
On Mon, Jun 20, 2011 at 20:43 +1000, James Morris wrote:
> 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?
This is a PoC of ~user/.ssh/authorized_keys presence infoleak (and
whether it is empty) using taskstats interface:
http://www.openwall.com/lists/oss-security/2011/06/21/12
/proc/PID/io can be used too.
More close interaction with ssh client would gain authorized_keys' size or,
probably, what pam module denied the access.
Thanks,
--
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
next prev parent reply other threads:[~2011-06-21 18:28 UTC|newest]
Thread overview: 28+ 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 ` [kernel-hardening] Re: [RFC 2/5 v4] procfs: add hidepid= and gid= mount options James Morris
2011-06-20 5:07 ` James Morris
2011-06-20 10:39 ` [kernel-hardening] " Vasiliy Kulikov
2011-06-20 10:39 ` Vasiliy Kulikov
2011-06-20 10:43 ` [kernel-hardening] " James Morris
2011-06-20 10:43 ` James Morris
2011-06-20 11:23 ` [kernel-hardening] " KOSAKI Motohiro
2011-06-20 11:23 ` KOSAKI Motohiro
2011-06-20 17:06 ` [kernel-hardening] " Vasiliy Kulikov
2011-06-20 17:06 ` Vasiliy Kulikov
2011-06-20 19:41 ` [kernel-hardening] " Eric W. Biederman
2011-06-20 19:41 ` Eric W. Biederman
2011-06-20 23:19 ` [kernel-hardening] " James Morris
2011-06-20 23:19 ` James Morris
2011-06-21 18:28 ` Vasiliy Kulikov [this message]
2011-06-21 18:28 ` Vasiliy Kulikov
2011-06-20 13:58 ` [kernel-hardening] " Alexey Dobriyan
2011-06-20 13:58 ` Alexey Dobriyan
2011-06-20 14:11 ` [kernel-hardening] " Solar Designer
2011-06-20 14:19 ` Vasiliy Kulikov
2011-06-20 14:25 ` Solar Designer
2011-06-20 14:35 ` Vasiliy Kulikov
2011-06-20 14:47 ` Solar Designer
2011-06-20 15:00 ` Vasiliy Kulikov
2011-06-20 13:31 ` [kernel-hardening] " Solar Designer
2011-06-20 13:31 ` Solar Designer
2011-06-15 18:51 [kernel-hardening] " Vasiliy Kulikov
2011-06-16 2:24 ` [kernel-hardening] " 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=20110621182827.GA8960@albatros \
--to=segoon@openwall.com \
--cc=jmorris@namei.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.