From: Arjan van de Ven <arjan@infradead.org>
To: regatta <regatta@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FS possible security exposure ?
Date: Sun, 25 Dec 2005 10:40:00 +0100 [thread overview]
Message-ID: <1135503601.2946.6.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <5a3ed5650512250129t434d2b42kc1ebac1c5b308986@mail.gmail.com>
> (when you have hundred of users and hundred of NFS and thousand of
> net groups you don't want a user to edit other file just because he
> has write permission in the patent dir).
if you have write permission in the directory you're allowed to
1) create new files
2) rename existing files
3) delete files
4) rename files over existing files (combo of 2 and 3 sort of)
so an "edit" as you describe is
* create a new file with the new (eg modified) content
* rename the new file over the existing file
that's how reliable editors operate (the rename-over-file is an atomic
operation) to avoid any possibility of dataloss due to crashes etc.
Since the 1-4 rules are pretty much there for all unixes...
Maybe your solaris editor doesn't do editing in this way?
next prev parent reply other threads:[~2005-12-25 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-25 9:29 regatta
2005-12-25 9:40 ` Arjan van de Ven [this message]
2005-12-25 10:10 ` regatta
2005-12-25 10:12 ` Wichert Akkerman
2005-12-25 10:17 ` Arjan van de Ven
2005-12-25 11:42 ` regatta
2005-12-25 9:45 ` Trond Myklebust
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=1135503601.2946.6.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regatta@gmail.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 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®