[7133] in bugtraq
Re: non-exec stacks on solaris.
daemon@ATHENA.MIT.EDU (Casper Dik)
Wed Jul 1 13:17:18 1998
Date: Wed, 1 Jul 1998 15:17:22 +0200
Reply-To: Casper Dik <casper@HOLLAND.SUN.COM>
From: Casper Dik <casper@HOLLAND.SUN.COM>
X-To: Darren Reed <avalon@coombs.anu.edu.au>
To: BUGTRAQ@NETSPACE.ORG
In-Reply-To: Your message of "Wed, 01 Jul 1998 23:09:33 +1000."
<199807011309.GAA15049@earth.sun.com>
>
>not long ago, someone posted that you can disable execution of
>instructions on the stack via /etc/system for solaris. There
>appears to be three variables for this:
>
>noexec_user_stack
>noexec_user_stack_log
>noexec_zfod_argsp
>
>The first two are pretty obvious, but what about the third ?
The first two (new in 2.6) are, indeed, obvious. (Note that they
exist in all kernels but only work on sun4m/sun4d and Ultras)
Noexec_zfod_argsp is the variable used by the mechanism internally;
it's the argument pointer used to initialize the page protection
by the stack. It's not a variable you can set.
(i.e., the variable contains the protection bits as used on a
"noexec" zero-fill-on-demand page.
Casper
