From: Vasiliy Kulikov <segoon@openwall.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
"David S. Miller" <davem@davemloft.net>,
Arnd Bergmann <arnd@arndb.de>,
Nikanth Karthikesan <knikanth@suse.de>,
David Rientjes <rientjes@google.com>,
Matt Mackall <mpm@selenic.com>,
linux-doc@vger.kernel.org
Subject: [kernel-hardening] Re: [RFC 5/5 v3] procfs: add documentation for procfs mount options
Date: Wed, 15 Jun 2011 20:31:48 +0400 [thread overview]
Message-ID: <20110615163147.GA17087@albatros> (raw)
In-Reply-To: <20110615092221.b143c45a.rdunlap@xenotime.net>
On Wed, Jun 15, 2011 at 09:22 -0700, Randy Dunlap wrote:
> On Wed, 15 Jun 2011 17:58:19 +0400 Vasiliy Kulikov wrote:
> > +hidepid=1 means users may not access any /proc/<pid>/ directories, but their
>
> comma not needed above. [...]
Indeed, thank you for the fixes!
--
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: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
"David S. Miller" <davem@davemloft.net>,
Arnd Bergmann <arnd@arndb.de>,
Nikanth Karthikesan <knikanth@suse.de>,
David Rientjes <rientjes@google.com>,
Matt Mackall <mpm@selenic.com>,
linux-doc@vger.kernel.org
Subject: Re: [RFC 5/5 v3] procfs: add documentation for procfs mount options
Date: Wed, 15 Jun 2011 20:31:48 +0400 [thread overview]
Message-ID: <20110615163147.GA17087@albatros> (raw)
In-Reply-To: <20110615092221.b143c45a.rdunlap@xenotime.net>
On Wed, Jun 15, 2011 at 09:22 -0700, Randy Dunlap wrote:
> On Wed, 15 Jun 2011 17:58:19 +0400 Vasiliy Kulikov wrote:
> > +hidepid=1 means users may not access any /proc/<pid>/ directories, but their
>
> comma not needed above. [...]
Indeed, thank you for the fixes!
--
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
next prev parent reply other threads:[~2011-06-15 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 13:58 [kernel-hardening] [RFC 5/5 v3] procfs: add documentation for procfs mount options Vasiliy Kulikov
2011-06-15 13:58 ` Vasiliy Kulikov
2011-06-15 16:22 ` [kernel-hardening] " Randy Dunlap
2011-06-15 16:22 ` Randy Dunlap
2011-06-15 16:31 ` Vasiliy Kulikov [this message]
2011-06-15 16:31 ` 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=20110615163147.GA17087@albatros \
--to=segoon@openwall.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=kernel-hardening@lists.openwall.com \
--cc=knikanth@suse.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=rdunlap@xenotime.net \
--cc=rientjes@google.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 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.