[lkml]   [2001]   [Oct]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectvfat permissions (umask, noexec) brokeness (once more ...)

as we all know, the noexec handling was changed in 2.4.10. now some
people claim, that using umask=111 is the right way to get the old
behaviour - but that's _wrong_. as opposed to their statements, vfat's
umask= does _not_ apply only to regular files, but also to directories
(you just don't notice it when you run as root) - and it's right that
way, as otherwise you could not specify umask=77 to lock out all users
but the owner specified by uid= & gid=.
i see two possible solutions: a new flag "noexecbits" which works like
the old (=broken) "noexec" or two different umasks (like samba does):
one for directories and one for regular files.
btw, the "showexec" flag is a big improvement to the situation, but i
still don't like it, as the files just are not executable without major
magic ...


ps: cc me, i'm not on the list.

Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
Nothing is fool-proof to a sufficiently talented fool.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:08    [W:0.021 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site