From: Al Viro <viro@ZenIV.linux.org.uk>
To: Stepan Chatalyan <kehcho@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hi all, bug or design flaw?
Date: Fri, 22 Jan 2010 01:25:44 +0000 [thread overview]
Message-ID: <20100122012544.GV19799@ZenIV.linux.org.uk> (raw)
In-Reply-To: <22d9728d1001211705i4cf90df2ha730061ea01972b6@mail.gmail.com>
On Fri, Jan 22, 2010 at 02:05:50AM +0100, Stepan Chatalyan wrote:
> (1) I mount /tmp with noexec,nosuid,nodev options
> (4) I tried to execute it, but pass to bash ". /tmp/createdfile"
>
> [kehcho@tornadowt] [/tmp]$ . /tmp/createdfile
> Probe...
>
> It is a kernel bug or I just report a another one?
What the hell does it have to do with the kernel? You've told shell
to open a text file, read it and interpret its contents line by line.
It had done as instructed. Moreover, bash /tmp/createdfile would work
just as fine. Neither of those would attempt to do execve() on the
file in question; you are just telling shell what to open and read.
next prev parent reply other threads:[~2010-01-22 1:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 1:05 Hi all, bug or design flaw? Stepan Chatalyan
2010-01-22 1:12 ` andrew hendry
2010-01-22 1:25 ` Al Viro [this message]
2010-01-22 2:00 ` Shu Wu
2010-01-22 2:15 ` Daniel Hazelton
2010-01-22 2:25 ` Américo Wang
2010-01-22 11:30 ` Alan Cox
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=20100122012544.GV19799@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=kehcho@gmail.com \
--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