On Sep 24, 2005, at 03:01:50, Al Viro wrote:
And O_DIRECTORY is not the only flag that acquires or loses meaning
depending on O_CREAT - consider e.g. O_EXCL. It's a mess, of
course, but this mess is part of userland ABI. We tried to fix
symlink idiocy, BTW, on the assumption that nothing would be
relying on it. Didn't work...
Maybe CONFIG_FIX_CRAPPY_ABI_CORNER_CASES? If the user is willing to
deal with some minimal breakage and fix programs relying on icky
unsupported behavior, then they could turn that on for a slightly
more secure system. Make it depend on "experimental" and give it big
warning messages. It's likely that some of the more-secure server-
oriented distros that run patched gcc and such to avoid buffer
overflow and such might turn it on.
Cheers,
Kyle Moffett
--
Simple things should be simple and complex things should be possible
-- Alan Kay
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |