not talking about doing it on all platforms (if ia32 sucks) or
making it default, just to give us security minded admins and users a kernel
option.
br
db
___
freebsd-security@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-secu
an be writable and readable. When it is readable it is
also executable. On other arch's like AMD64 and IA64, I believe memory can be
readable, writable and executable. Therefore I would like to remove the
executable bit on the stack and heap for the systems su
t;
> It appears that propolice has finally made its way into gcc 4.1, so
> hopefully that will be ready for FreeBSD 7.
I don't want a gcc fix via propolice, I want kernel support for this. So that
if a program tries to execute code in the stack or
ng that kernel
support is best performancewise (on platforms with hardware support for
this). But thanks for your input, I also use php and postgresql, so it is
nice to know that they will work :-)
br
db
___
freebsd-security@freebsd.org mailing list
h
AMD64, I think it must be the cheapest of the platforms with
hardware support for execute and read permission distinction on memory?
Best regards
db
___
freebsd-security@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> ports will break, if you play with it you can disable it by default and
> enable it explicit when you are willing to compile a binary with it.
Ok thanks, but I was looking for a kernel level patch. Btw which ports will
break?
br
db
___
freebsd-
Hi all
Does FreeBSD support a non-executable stack on any of the tier 1 and 2
platforms that has this feature?
If not, are there any plans of implementing this and is there a patch I can
use for 6.0 (when it is released)?
Best regards
db
___
freebsd
