Messages in this thread |  | | Subject | Re: [RFC] "Text file busy" when overwriting libraries | Date | Sun, 14 Oct 2001 13:08:28 +0100 (BST) | From | Alan Cox <> |
| |
> My big question is how to correctly define O_EXEC for every > architecture. But I would like to know if there are objectionable > parts as well.
It looks totally unworkable. Open() has side effects on a large number of platforms, and being able to open an exec only file might trigger them as well as all sorts of other potential problems where files are marked rwx by accident as is very common.
You narrow the DoS vulnerability and add a whole new set of open based ones.
This isnt a problem worth solving. Shared libraries are managed by the superuser. The shared library tools already do the right thing. The superuser can equally reboot the machine or reformat the disk by accident anyway. - 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/
|  |