From 42156b5190f4fa150e1fab6777eb81e69d4db8c9 Mon Sep 17 00:00:00 2001 From: Igor Pashev Date: Sat, 13 May 2017 13:54:49 +0300 Subject: Imported gcc-6 (6.3.0-17) --- debian/README.ssp | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 debian/README.ssp (limited to 'debian/README.ssp') diff --git a/debian/README.ssp b/debian/README.ssp new file mode 100644 index 0000000..9facca7 --- /dev/null +++ b/debian/README.ssp @@ -0,0 +1,28 @@ +Stack smashing protection is a feature of GCC that enables a program to +detect buffer overflows and immediately terminate execution, rather than +continuing execution with corrupt internal data structures. It uses +"canaries" and local variable reordering to reduce the likelihood of +stack corruption through buffer overflows. + +Options that affect stack smashing protection: + +-fstack-protector + Enables protection for functions that are vulnerable to stack + smashing, such as those that call alloca() or use pointers. + +-fstack-protector-all + Enables protection for all functions. + +-Wstack-protector + Warns about functions that will not be protected. Only active when + -fstack-protector has been used. + +Applications built with stack smashing protection should link with the +ssp library by using the option "-lssp" for systems with glibc-2.3.x or +older; glibc-2.4 and newer versions provide this functionality in libc. + +The Debian architectures alpha, hppa, ia64, m68k, mips, mipsel do not +have support for stack smashing protection. + +More documentation can be found at the project's website: +http://researchweb.watson.ibm.com/trl/projects/security/ssp/ -- cgit v1.2.3