From: Andreas Dilger <adilger@turbolabs.com>
To: Andris Pavenis <pavenis@latnet.lv>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.11: mount flag noexec still broken for VFAT partition
Date: Wed, 10 Oct 2001 15:13:33 -0600 [thread overview]
Message-ID: <20011010151333.G10443@turbolinux.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0110102258290.28429-100000@gulbis.latnet.lv>
In-Reply-To: <Pine.LNX.4.21.0110102258290.28429-100000@gulbis.latnet.lv>
On Oct 10, 2001 23:01 +0300, Andris Pavenis wrote:
> Similary as with 2.4.10 mount flag noexec does not work for VFAT
> partition. I have following in fstab
>
> /dev/hda1 /c vfat noexec,gid=201,umask=002,quiet 1 0
> /dev/hda5 /d vfat noexec,gid=201,umask=002,quiet 1 0
>
> but I see that all files in corresponding filesystems are still
> exectuable
Probably because your uid or gid match the above, so your access permission
is done by checking "user" or "group" and not "other". Try "umask=113"
instead.
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-10-10 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 20:01 2.4.11: mount flag noexec still broken for VFAT partition Andris Pavenis
2001-10-10 21:13 ` Andreas Dilger [this message]
2001-10-10 22:36 ` Marko Kreen
2001-10-11 1:10 ` H. Peter Anvin
2001-10-11 2:04 ` Marko Kreen
2001-10-11 2:07 ` [RFC] behaviour of stat() variants (was Re: 2.4.11: mount flag noexec still broken for VFAT partition) Alexander Viro
2001-10-11 6:09 ` 2.4.11: mount flag noexec still broken for VFAT partition Andris Pavenis
2001-10-11 8:14 ` linux-2.4.11-dontuse Why? Sergey S. Kostyliov
2001-10-11 10:12 ` Morten Helgesen
2001-10-11 19:18 ` 2.4.11: mount flag noexec still broken for VFAT partition Peter Bornemann
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=20011010151333.G10443@turbolinux.com \
--to=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavenis@latnet.lv \
/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.