Messages in this thread | | | Date | Wed, 7 May 2003 15:04:57 -0400 | From | Chuck Ebbert <> | Subject | Re: The disappearing sys_call_table export. |
| |
>> Preloading libraries, ptracing init, patching g/libc, etc. are >> obviously not the way to go. > > those obviously need to be implemented via the security subsystem (eg > LSM). Hooks are obviously the wrong level to do things and I could even > tell you that you cannot implement this right from a module actually.
What is really needed is some kind of proper generic hooking setup that could be used both by LSM and other things. People doing this may need to intercept syscalls both on their way to the kernel and on the way back to userland (so they can see return codes.) They may also need to say whether they want to be first or last if there are multiple users of this facility.
But the real question is why the export of sys_call_table was so gratuitously removed without any kind of replacement being offered. And the attitude of the developers about it is truly awful. ("Oh, so we broke the drivers you depend on for your livelihood? You can just go get a new job -- pounding sand down a rathole.")
- 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/
| |