9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] remove files in /srv
Date: Mon, 31 Jan 2005 22:56:17 -0500	[thread overview]
Message-ID: <ee9e417a050131195635420e71@mail.gmail.com> (raw)
In-Reply-To: <05b7ca7e8285696ad011d8d8b359dc20@orthanc.cc.titech.ac.jp>

 > Anyone can replace files in /srv.  Bad things won't
> happen if /srv/boot has been replaced by a malicious user?

#s/boot is explicitly unremovable.

> Therefore, how about changing '#s' so that only file owner
> or host owner can remove the file?

This won't work well.  9fs alice creates /srv/alice as the user
who runs it, but if the connection is lost and someone else
runs 9fs alice, then they need permission to remove it and
replace it. 

It's not at all clear what the right answer is.  The users have
to trust themselves in /srv.

Russ


  parent reply	other threads:[~2005-02-01  3:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-01  1:11 YAMANASHI Takeshi
2005-02-01  3:21 ` arisawa
2005-02-01  3:56 ` Russ Cox [this message]
2005-02-01  3:48 YAMANASHI Takeshi
2005-02-01  4:06 ` arisawa
2005-02-01  4:33   ` Russ Cox
2005-02-01 20:31     ` rog
2005-02-02 23:22       ` Bruce Ellis
2005-02-02 23:57         ` Charles Forsyth
2005-02-01  4:05 YAMANASHI Takeshi
2005-02-01  4:44 ` geoff

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=ee9e417a050131195635420e71@mail.gmail.com \
    --to=russcox@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).