![]() | |||||||||||||
Messages in this thread |
Am Freitag den, 6. September 2002, um 12:04, schrieb Pavel Machek: > Hi!>>>> That is the fundamental problem with a userspace shared memory >>> implementation: write permissions on a message queue should grant >>> mq_send(), but write permissions on shared memory grant a lot more >>> than>>> just that.>>>> is it really a problem? As long as the read and write queues are >> separated>> per sender, all that can happen is that a sender is allowed to read his >> own messages - that is not an exciting capability.>> Imagine something that writes data into the que then erases the data and > gets rid of setuid.> Well, I can imagine that - but what do you mean by that? Do you mean: replacing the data with shellcode, manipulating the length field for provoking buffer overflows? - 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/ | ||||||||||||
| Last update: 2005-03-22 12:28 [from the cache] ©2003-2008 | |||||||||||||