All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas McNaught <doug@mcnaught.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Mark Rosenstand <mark@borkware.net>, linux-kernel@vger.kernel.org
Subject: Re: Executable shell scripts
Date: Sat, 13 May 2006 07:19:21 -0400	[thread overview]
Message-ID: <87r72yi346.fsf@suzuka.mcnaught.org> (raw)
In-Reply-To: <1147518432.3217.2.camel@laptopd505.fenrus.org> (Arjan van de Ven's message of "Sat, 13 May 2006 13:07:12 +0200")

Arjan van de Ven <arjan@infradead.org> writes:

> On Sat, 2006-05-13 at 13:03 +0200, Mark Rosenstand wrote:

>> bash-3.00$ cat << EOF > test
>> > #!/bin/sh
>> > echo "yay, I'm executing!"
>> > EOF
>> bash-3.00$ chmod 111 test
>> bash-3.00$ ./test
>> /bin/sh: ./test: Permission denied
>
> is your script readable as well? 111 is just weird/odd.

It needs to be readable as well.  What ends up happening is that the
kernel sees the execute bit, looks at the shebang line and then does:

/bin/sh test

Since read permission is off, the shell's open() call fails.  It will
work fine if you use 755 as the permissions.

Every Unix I've ever seen works this way.  It'd be nice to have
unreadable executable scripts, but no one's ever done it.

-Doug

  parent reply	other threads:[~2006-05-13 11:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-13 10:38 Executable shell scripts Mark Rosenstand
2006-05-13 10:56 ` Arjan van de Ven
2006-05-13 11:03   ` Mark Rosenstand
2006-05-13 11:07     ` Arjan van de Ven
2006-05-13 11:17       ` Mark Rosenstand
2006-05-13 11:18       ` Willy Tarreau
2006-05-13 11:19       ` Douglas McNaught [this message]
2006-05-13 11:27         ` Mark Rosenstand
2006-05-13 11:37           ` Joel Jaeggli
2006-05-13 12:59           ` Theodore Tso
2006-05-13 13:18             ` Mark Rosenstand
2006-05-13 22:42               ` Neil Brown
2006-05-13 11:28         ` Stefan Smietanowski
2006-05-13 11:37           ` Neil Brown
2006-05-13 12:45             ` Willy Tarreau
2006-05-13 14:00         ` Arjan van de Ven
2006-05-13 20:52           ` Douglas McNaught
2006-05-13 11:16     ` J.A. Magallón
2006-05-13 11:22     ` Bernd Petrovitsch
2006-05-13 11:45       ` Mark Rosenstand
2006-05-13 11:56         ` Bernd Petrovitsch
2006-05-13 12:23           ` Mark Rosenstand
2006-05-13 12:58             ` Willy Tarreau
2006-05-13 18:55             ` Bernd Petrovitsch
2006-05-13 11:23     ` CaT
2006-05-13 11:00 ` Willy Tarreau

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=87r72yi346.fsf@suzuka.mcnaught.org \
    --to=doug@mcnaught.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@borkware.net \
    /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.