From: Kyle Moffett <mrmacman_g4@mac.com>
To: Hauke Laging <mailinglisten@hauke-laging.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VFS: Dynamic umask for the access rights of linked objects
Date: Tue, 28 Feb 2006 23:21:37 -0500 [thread overview]
Message-ID: <08AB14CC-2BB2-4923-BFDB-B1360B5EF405@mac.com> (raw)
In-Reply-To: <200603010454.15223.mailinglisten@hauke-laging.de>
On Feb 28, 2006, at 22:54:15, Hauke Laging wrote:
> 6) In my scenario the VFS would add a step after 4): It would check
> if the symlink has been created by someone different from the
> process's uid and from root. If so there is the risk of abuse and
> the access check would be repeated for the symlink owner.
>
> 7) The VFS would find out that the symlink owner is not allowed to
> write to /etc/passwd. Thus the write access is prohibited, even for
> a process with superuser rights.
Feel free to write an LSM to do this, but it breaks POSIX specs a bit
and could cause problems with some programs, so it's not likely to
become the default behavior.
Cheers,
Kyle Moffett
next prev parent reply other threads:[~2006-03-01 4:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 2:28 Hauke Laging
2006-03-01 2:45 ` Sam Vilain
2006-03-01 3:54 ` Hauke Laging
2006-03-01 4:21 ` Kyle Moffett [this message]
2006-03-01 7:59 ` Chris Wright
2006-03-02 16:11 ` Jiri Kosina
2006-03-01 16:33 ` Horst von Brand
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=08AB14CC-2BB2-4923-BFDB-B1360B5EF405@mac.com \
--to=mrmacman_g4@mac.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mailinglisten@hauke-laging.de \
/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®