Date: Tue, 04 Mar 1997 11:12:43 -0700 From: Warner Losh <imp@village.org> To: Bruce Evans <bde@zeta.org.au> Cc: terry@lambert.org, wpaul@skynet.ctr.columbia.edu, hackers@freebsd.org Subject: Re: Removing execute privs from stack pages Message-ID: <E0w1yhg-0000oP-00@rover.village.org> In-Reply-To: Your message of "Tue, 04 Mar 1997 22:32:08 %2B1100." <199703041132.WAA06944@godzilla.zeta.org.au> References: <199703041132.WAA06944@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199703041132.WAA06944@godzilla.zeta.org.au> Bruce Evans writes: : >Frankly, I wonder how LISP and FORTH can run on such a system. : : I think they would have to do system calls to map pages for execution. : Even dynamically linked C code would need this. There would be some : security if the mapping were refused for setuid processes. g++ uses trampoline code on the stack as well for things like nested scopes and references/pointers to functions inside those scopes. There was also some traffic that g++ placed other things on the stack as well with its new exception handling code, but I'm not sure if that is for x86 or not. Neat idea, too bad otehr people need the stack to be executable :-(. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0w1yhg-0000oP-00>