From: Andreas Dilger <adilger@turbolabs.com>
To: Peter Bornemann <eduard.epi@t-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: noexec-flag does not work in Linux 2.4.10-pre10
Date: Thu, 20 Sep 2001 15:17:08 -0600 [thread overview]
Message-ID: <20010920151708.F14526@turbolinux.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109201957530.2448-100000@eduard.t-online.de>
In-Reply-To: <Pine.LNX.4.33.0109201957530.2448-100000@eduard.t-online.de>
On Sep 20, 2001 20:05 +0200, Peter Bornemann wrote:
> It seems that the noexec in fstab no longer works. Is this
> intentional?
>
> In fstab I have the following line:
>
> /dev/hda1 /dosc vfat codepage=850,umask=000,noexec 0 0
>
> A ls -l in /dosc shows:
>
> -rwxrwxrwx 1 root root 267657216 Jun 28 22:34 win386.swp
>
> The same case with iso9660:
>
> -r-xr-xr-x 1 root root 0 Jan 24 2000 s3cd1.dat
>
> However umask=111 is still working. I don't know exactly when this
> happened, but it was hot there in earlier 2.4 kernels.
Are you sure this is actually a problem? Can you really exec these
files, or is it just a matter of the flag? Some changes were made
to mount flags by Al Viro. If you really want the flags gone, you
should use a different umask (e.g. umask=111). The noexec flag
means (for filesystems that actually have permissions) that _even if_
the "x" bit is set, it cannot be executed.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-09-20 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 18:05 noexec-flag does not work in Linux 2.4.10-pre10 Peter Bornemann
2001-09-20 21:17 ` Andreas Dilger [this message]
2001-09-20 23:24 ` Peter Bornemann
2001-09-20 23:39 ` Alexander Viro
2001-09-21 10:51 ` Padraig Brady
2001-09-20 21:17 ` Alexander Viro
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=20010920151708.F14526@turbolinux.com \
--to=adilger@turbolabs.com \
--cc=eduard.epi@t-online.de \
--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 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.