lkml.org 
[lkml]   [2006]   [Mar]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    Subject[Patch 3 of 8] Introduce a config option for stack-protector
    From
    Date
    This patch adds the config options for -fstack-protector

    Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>

    ---
    arch/x86_64/Kconfig | 25 +++++++++++++++++++++++++
    1 file changed, 25 insertions(+)

    Index: linux-2.6.16-rc6-stack-protector/arch/x86_64/Kconfig
    ===================================================================
    --- linux-2.6.16-rc6-stack-protector.orig/arch/x86_64/Kconfig
    +++ linux-2.6.16-rc6-stack-protector/arch/x86_64/Kconfig
    @@ -462,6 +462,31 @@ config SECCOMP

    If unsure, say Y. Only embedded should say N here.

    +config STACK_PROTECTOR
    + bool "Enable -fstack-protector buffer overflow detection (EXPRIMENTAL)"
    + depends on EXPERIMENTAL
    + default n
    + help
    + This option turns on the -fstack-protector GCC feature that is new
    + in GCC version 4.1. This feature puts, at the beginning of
    + critical functions, a canary value on the stack just before the return
    + address, and validates the value just before actually returning.
    + Stack based buffer overflows that need to overwrite this return
    + address now also overwrite the canary, which gets detected.
    +
    + NOTE NOTE NOTE
    + At this point this requires a special, patched GCC compiler!
    + Do not enable this unless you are using such a compiler.
    +
    +config STACK_PROTECTOR_ALL
    + bool "Use stack-protector for all functions"
    + depends on STACK_PROTECTOR
    + default n
    + help
    + Normally, GCC only inserts the canary value protection for
    + functions that use large-ish on-stack buffers. By enabling
    + this option, GCC will be asked to do this for ALL functions.
    +
    source kernel/Kconfig.hz

    endmenu
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-03-17 17:20    [W:0.032 / U:180.804 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site