Messages in this thread |  | | Date | Sun, 14 Oct 2001 11:48:44 +0200 | Subject | vfat permissions (umask, noexec) brokeness (once more ...) | From | Oswald Buddenhagen <> |
| |
hi,
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 ...
greetings
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 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/
|  |