No description
Find a file
Daniel Micay 8765b1035f enable -fstack-protector-strong
This results in nearly all functions with the possibility of stack
corruption getting stack canaries, because it applies to any function
taking a reference to the frame or with a local array rather than just
the functions with arrays larger than 8 bytes. It was developed for use
in Chrome (and Chrome OS) and has also been adopted by various other
distributions (Arch, Fedora, Ubuntu, etc).

The code size increase ranges from ~1.5% to ~2.5%, compared to ~0.3% to
~0.7% with the more conservative switch. The increase in the performance
loss is usually minimal. The overall size increase once everything other
than C and C++ code is taken into account is minimal, and it greatly
improves the mitigation of stack buffer overflow vulnerabilities.

https://lwn.net/Articles/584225/

Change-Id: Ie83d381e09d94deb34c5ff142a101ba3d14cf3ba
2015-12-05 01:52:45 -05:00
core enable -fstack-protector-strong 2015-12-05 01:52:45 -05:00
libs/host Add LOCAL_MODULE_HOST_OS 2015-09-03 16:40:51 -07:00
target selinux: Grant all processes the domain_deprecated attribute 2015-11-04 08:49:07 -08:00
tools Use explicitly sized types in zipalign/ziptime 2015-11-04 23:52:52 +00:00
.gitignore Add build subprojects to .gitignore 2015-07-23 13:18:47 -07:00
buildspec.mk.default Remove WEBCORE_INSTRUMENTATION and ENABLE_SVG 2013-07-25 15:52:17 -07:00
CleanSpec.mk Fix issie #23116383: Include security patch level in Settings 2015-08-12 16:29:08 -07:00
envsetup.sh Merge "build: Add support for defining products in /product" 2015-11-02 22:27:08 +00:00