public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Jaegermann <michal@harddata.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: rootfs exposure in /proc/mounts
Date: Sun, 27 Oct 2002 16:27:55 -0700	[thread overview]
Message-ID: <20021027162755.A19334@mail.harddata.com> (raw)
In-Reply-To: <20021027111856.GA789@alpha.home.local>; from willy@w.ods.org on Sun, Oct 27, 2002 at 12:18:56PM +0100

On Sun, Oct 27, 2002 at 12:18:56PM +0100, Willy Tarreau wrote:
> And I also
> agree that mtab shouldn't be under /etc (this is the only file that needs to
> be written to). At least, it should be moved to /var/state or something like
> that, provided it's available early in the boot stage,

I was just looking at these things I found few more such files in
/etc.  Like /etc/adjtime, /etc/mrtg/<something> and /etc/.aumixrc.
I consider all of these user-space bugs.  There are also /etc/passwd
and /etc/shadow which will be written to if you are changing
passwords while not using something like NIS.  This is, in a sense,
a harder case but one can live with that.

   Michal

  reply	other threads:[~2002-10-27 23:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-26 18:53 rootfs exposure in /proc/mounts Andreas Steinmetz
2002-10-26 18:59 ` Alexander Viro
2002-10-26 19:12   ` Andreas Steinmetz
2002-10-26 19:26     ` Jeff Garzik
2002-10-27  0:22       ` Andreas Steinmetz
2002-10-27 10:21       ` Andreas Haumer
2002-10-27 11:18         ` Willy Tarreau
2002-10-27 23:27           ` Michal Jaegermann [this message]
2002-10-28  9:05           ` Kasper Dupont
2002-10-27 15:02         ` Jeff Garzik
2002-10-27 15:09           ` Christoph Hellwig
2002-10-28  0:03             ` Kenneth Johansson
2002-10-28  0:18               ` Christoph Hellwig
2002-10-28  1:17                 ` Rob Landley
2002-10-28 15:01                   ` Christoph Hellwig

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=20021027162755.A19334@mail.harddata.com \
    --to=michal@harddata.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@w.ods.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox