From: daw@mozart.cs.berkeley.edu (David Wagner)
To: linux-kernel@vger.kernel.org
Subject: Re: question: permission checking for network filesystem
Date: 21 May 2001 03:04:05 GMT [thread overview]
Message-ID: <9ea0j5$ik$1@abraham.cs.berkeley.edu> (raw)
In-Reply-To: <20010520172948.A27935@artax.karlin.mff.cuni.cz> <Pine.LNX.3.96.1010521001448.31037A-100000@artax.karlin.mff.cuni.cz>
Mikulas Patocka wrote:
>If you are checking permissions on server, read/execute have no security
>meaning.
This seems a bit too strong. If I try to exec a file that has read
permission enabled but not execute permission, I'd like this to fail.
You can just imagine sysadmins who turn off exec bits on old buggy apps
to prevent users from executing them, who could get bit in the butt by
the sort of unexpected behavior that would result from ignoring execute
permission bits.
next prev parent reply other threads:[~2001-05-21 3:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-20 15:29 question: permission checking for network filesystem Jan Hudec
2001-05-20 22:49 ` Mikulas Patocka
2001-05-21 3:04 ` David Wagner [this message]
2001-05-21 13:32 ` Jan Hudec
2001-05-21 22:26 ` Mikulas Patocka
2001-05-22 8:10 ` Jan Hudec
[not found] ` <200105220602.f4M62N364271@saturn.cs.uml.edu>
2001-05-24 12:52 ` Jan Hudec
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='9ea0j5$ik$1@abraham.cs.berkeley.edu' \
--to=daw@mozart.cs.berkeley.edu \
--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