All of lore.kernel.org
 help / color / mirror / Atom feed
From: Solar Designer <solar@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: Re: [kernel-hardening] [RFC 2/5 v4] procfs: add hidepid= and gid= mount options
Date: Mon, 20 Jun 2011 18:11:37 +0400	[thread overview]
Message-ID: <20110620141137.GA31044@openwall.com> (raw)
In-Reply-To: <BANLkTimb==tuDKQ2jyYS+Py0FfNxKVc+Pg@mail.gmail.com>

Vasiliy -

On Mon, Jun 20, 2011 at 04:58:10PM +0300, Alexey Dobriyan wrote:
> gid= is bad choice because
> a) e. g. VFAT uses uid=/gid= mount options to make all inodes to have
> certain uid/gid
> b) uid=/gid=, IIRC, will be added as generic VFS mount options (like ro)
>    with semantics described in a)
> 
> so having different semantics for /proc won't be good.

I lost track of your proposals/patches.  Aren't you currently proposing
that gid= would make all inodes have the specified gid?  If not, why
not?  Such semantics sound fine to me.  That's what gid= does on procfs
on Linux 2.4.x-ow.

Please explain.

Thanks,

Alexander

  reply	other threads:[~2011-06-20 14:11 UTC|newest]

Thread overview: 27+ 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       ` [kernel-hardening] " Vasiliy Kulikov
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       ` Solar Designer [this message]
2011-06-20 14:19         ` [kernel-hardening] " 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

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=20110620141137.GA31044@openwall.com \
    --to=solar@openwall.com \
    --cc=kernel-hardening@lists.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 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.