Re: non-exec stack

From: Borja Marcos (borjamar@sarenet.es)
Date: 07/11/01 

From: Borja Marcos <borjamar@sarenet.es>
To: freebsd-security@freebsd.org
Date: Wed, 11 Jul 2001 22:35:50 +0200

On Wednesday 11 July 2001 21:17, you wrote:
> That's a different thing (it doesn't make the stack non-executable, it
> patches gcc to generate code which tries to catch and prevent
> stack-smashing buffer overflows). I don't know of anyone who has
> written a non-exec stack patch for FreeBSD. It would certainly be
> welcome.

        I wonder... how is it implemented? Perhaps checking that the page is not
a stack page whenever the process enters a system call? Checking the same
at context switches?

        Borja.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message

Relevant Pages

  • Re: non-exec stack
    ... >> patches gcc to generate code which tries to catch and prevent ... >> written a non-exec stack patch for FreeBSD. ... Kris ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)
  • Re: non-exec stack
    ... Most buffer overflow exploits are based on overwriting a function's return ... onto the stack. ... >> Is there is any non-exec stack kernel patch available for FreeBSD? ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)
  • Re: Unlimited threads being created
    ... Each thread has a stack, which requires memory from the process's ... thread must be considered by the scheduler every time the scheduler ... Thread context switches save the state of the processor to the ... space contention threads can cause in a single process is a much ...
    (comp.lang.java.programmer)