From: regatta <regatta@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FS possible security exposure ?
Date: Sun, 25 Dec 2005 13:10:16 +0300 [thread overview]
Message-ID: <5a3ed5650512250210w3528a8ccsb4df2c3a23863c40@mail.gmail.com> (raw)
In-Reply-To: <1135503601.2946.6.camel@laptopd505.fenrus.org>
I'm using Vi in Solaris and Vim in Linux, do you think this is the
problem ? (because when I use "echo BLABAL >> FILE_I_DONT_OWN_IT" it
will give me permission denied in Linux)
but if you think about it, how could the system allow the user to
modify a file that he don't own it and he don't have write privilege
on the file just because he has write in the parent directory ?
Maybe I'm wrong, but is this normal ? please let me know
BTW: is there any document, article or any page about this so I can
show it to my boss :)
Thanks
On 12/25/05, Arjan van de Ven <arjan@infradead.org> wrote:
>
> > (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?
>
>
>
>
--
Best Regards,
--------------------
-*- If Linux doesn't have the solution, you have the wrong problem -*-
next prev parent reply other threads:[~2005-12-25 10:10 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
2005-12-25 10:10 ` regatta [this message]
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=5a3ed5650512250210w3528a8ccsb4df2c3a23863c40@mail.gmail.com \
--to=regatta@gmail.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®