From: Joel Jaeggli <joelja@uoregon.edu>
To: Mark Rosenstand <mark@borkware.net>
Cc: Douglas McNaught <doug@mcnaught.org>,
arjan@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Executable shell scripts
Date: Sat, 13 May 2006 04:37:44 -0700 [thread overview]
Message-ID: <4465C508.6050201@uoregon.edu> (raw)
In-Reply-To: <20060513112754.1CA99146AF@hunin.borkware.net>
Mark Rosenstand wrote:
> Douglas McNaught <doug@mcnaught.org> wrote:
>> 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.
>
> According to
> http://www.faqs.org/faqs/unix-faq/faq/part4/section-7.html both 4.3BSD
> and SunOS have. I can confirm that it works on current BSD's as
> well.
The faq you're refering to is 10-12 years old. 4.3BSD isn't relevant to
anyone beyond historians at this point.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
-------------------------------------------------
Joel Jaeggli (joelja@uoregon.edu)
GPG Key Fingerprint:
5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2
next prev parent reply other threads:[~2006-05-13 11:39 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
2006-05-13 11:27 ` Mark Rosenstand
2006-05-13 11:37 ` Joel Jaeggli [this message]
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=4465C508.6050201@uoregon.edu \
--to=joelja@uoregon.edu \
--cc=arjan@infradead.org \
--cc=doug@mcnaught.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.