All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Huhn <C.Huhn@gsi.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: executable but not readable
Date: Mon, 29 Mar 2004 13:35:26 +0200	[thread overview]
Message-ID: <406809FE.5040100@gsi.de> (raw)
In-Reply-To: <1080328671.2480.23.camel@lade.trondhjem.org>

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

Hi again,

Trond Myklebust wrote:

>The point in the RFC is that the server should be looking
>at both the "executable" and the "read" bits when deciding whether or
>not to grant read access to the client.
>...
>  
>
>However if you really want to prevent OTHER+GROUP from reading and
>executing your shell scripts, then "chmod 500 /bin/ls.sh" is your
>simplest solution. That does the same thing on both the local and remote
>filesystems.
>  
>
I'm totally aware of the fact that this approach to enhance the security 
is dysfunctional and pretty lame [sigh].
Anyway, it was done like this in ancient days - and never worked but 
never did any harm either.

Now it's not working anymore and the only thing changed is the kernel.
So to get back to my initial question: *Is this a NFS bug?* Or has maybe 
something else changed  in the kernel?

Regards,
    Christopher

[-- Attachment #2: Type: text/html, Size: 1382 bytes --]

      parent reply	other threads:[~2004-03-29 11:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-25 18:00 executable but not readable Christopher Huhn
2004-03-25 18:37 ` Trond Myklebust
2004-03-26 10:48   ` Christopher Huhn
2004-03-26 19:17     ` Trond Myklebust
2004-03-27 12:17       ` Frank van Maarseveen
2004-03-28 23:46         ` Trond Myklebust
2004-03-28 23:59           ` Frank van Maarseveen
2004-03-29  1:00             ` Trond Myklebust
2004-03-29 11:35       ` Christopher Huhn [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=406809FE.5040100@gsi.de \
    --to=c.huhn@gsi.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.