diff options
author | Johannes Schindelin <johannes.schindelin@gmx.de> | 2019-06-27 02:29:02 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2019-06-27 12:53:45 -0700 |
commit | a1c5e906c8bab294f380151f59e552766fdf32b7 (patch) | |
tree | cbb0992d4b9b6dd1b2e3c5b93dfd6e38a15e015a /builtin/commit.c | |
parent | 8dca754b1e874719a732bc9ab7b0e14b21b1bc10 (diff) |
mingw: enable stack smashing protector
To reduce Git for Windows' attack surface, we started using the Address
Space Layout Randomization and Data Execution Prevention features in
ce6a158561f9 (mingw: enable DEP and ASLR, 2019-05-08).
To remove yet another attack vector, let's make use of gcc's stack
smashing protector that helps detect stack buffer overruns early.
Rather than using -fstack-protector, we use -fstack-protector-strong
because on Windows: The latter appears to strike a better balance
between the performance impact and the provided safety.
In a non-scientific test (time git log --grep=is -p), best of 5 timings
went from 23.009s to 22.997s, i.e. the performance impact was *well*
lost in the noise.
This fixes https://github.com/git-for-windows/git/issues/501
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/commit.c')
0 files changed, 0 insertions, 0 deletions