List, I searched the archives and could not find any reference to a non-executable stack discussion. Has their been any consideration given to setting the process level stacks to non-executable to help circumvent or at least reduce the problem of buffer overflow exploits. I know that OpenBSD has some work in this area, and was curious if Darwin was looking in this direction as well. Are their any gotcha's in either the GNU compiler or dynamic library loader mechanism that would make a non-executable stack difficult to do in Darwin? I read the MMU overview for the PowerPC and it seems that the MMU supports fairly granular execute privileges (IE per page versus per segment), which should make implementing the non-execute stack (and perhaps non-execute data segment) simpler. -Brian Tabone _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.