From: Bodo Eggert <7eggert@gmx.de>
To: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] Apply umask to /proc/<pid>
Date: Sun, 13 Mar 2005 02:23:32 +0100 [thread overview]
Message-ID: <E1DAHpO-0001a8-Mx@be1.7eggert.dyndns.org> (raw)
In-Reply-To: <fa.ft6scin.15lkbgv@ifi.uio.no>
Rene Scharfe <rene.scharfe@lsrfire.ath.cx> wrote:
> patch below makes procfs apply the umask of the processes to their
> respective /proc/<pid> directories and the files below them. That
> allows users to gain a bit of privacy by setting a restrictive umask in
> their profiles.
A [ur]limit-like value is fine, but allowing others to read the files you
put into a public directory should not imply giving up your privacy.
next parent reply other threads:[~2005-03-13 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ft6scin.15lkbgv@ifi.uio.no>
2005-03-13 1:23 ` Bodo Eggert [this message]
2005-03-12 21:12 Rene Scharfe
2005-03-13 5:10 ` Paul Jackson
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=E1DAHpO-0001a8-Mx@be1.7eggert.dyndns.org \
--to=7eggert@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.scharfe@lsrfire.ath.cx \
/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
all inboxes | Powered by JetHome®