Date: Sun, 30 Jun 2002 05:25:02 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Cedric Berger <cedric@wireless-networks.com> Cc: arch@freebsd.org Subject: Re: Time to make the stack non-executable? Message-ID: <3D1EF89E.B5BC0CCE@mindspring.com> References: <3D1E28ED.B67A5271@FreeBSD.org> <3D1E3126.C96FFAA5@mindspring.com> <3D1EF628.5090105@wireless-networks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Cedric Berger wrote: > It is the default (noexec_user_stack) for 64-bit Solaris. > http://docs.sun.com/?q=noexec_user_stack&p=/doc/806-7009/6jftnqsis&a=view > Since I doubt Sun would set a default which makes Java unusable, > It seems to me that Java has a good probability to be OK with that. > Or am I missing something? SPARC != i386. SunSpot uses executable stack on i386, according to one poster. However, this man page reference for Solaris gives a nice clue on how to get around it: explicit use of mprotect() (clever lads!). That actually gets rid of a lot of the objections I was able to come up with, if doing that to the stack would work on FreeBSD as well (seems to on 4.6). That leaves the issue of binary compatability; the sysctl approach (per Solaris) is not a good idea, since you can't stop other processes starting during an off-then-on-then-off window. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D1EF89E.B5BC0CCE>