mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: regatta <regatta@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FS possible security exposure ?
Date: Sun, 25 Dec 2005 10:45:42 +0100	[thread overview]
Message-ID: <1135503943.8032.8.camel@lade.trondhjem.org> (raw)
In-Reply-To: <5a3ed5650512250129t434d2b42kc1ebac1c5b308986@mail.gmail.com>

On Sun, 2005-12-25 at 12:29 +0300, regatta wrote:
> Hi everyone,
> 
> I have a question regarding how Linux handle the files permission ,
> here is what I found
> 
> When logged on to a Linux workstation a user can edit a file (even if
> the file on an NFS-mounted NAS directory) if he has write access at
> the directory level, even if the file is owned by root (or any other
> user) and is read-only.

Since you do not explain how you performed the test, it is hard to
comment, but I don't see this behaviour you describe:

trondmy@lade test$ ls -al
total 12
drwxrwxrwx   2 root root 4096 2005-12-25 10:42 .
drwxrwxrwt  10 root root 4096 2005-12-25 10:41 ..
-rw-r--r--   1 root root    5 2005-12-25 10:42 test
trondmy@lade test$ cat >test
bash: test: Permission denied


If I use 'vi' to edit the file, then it can be modified, but the way vi
does that is to delete the old file, and create a new one with the same
name (and it will only do this if you use 'w!'). That should ordinarily
work on Solaris too.

Cheers,
  Trond


      parent reply	other threads:[~2005-12-25  9:45 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
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 [this message]

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=1135503943.8032.8.camel@lade.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --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®