Browse Source

Merge pull request #1925 from Diapolo/gcc-hardening

GCC hardening for Bitcoin-Qt
miguelfreitas
Wladimir J. van der Laan 12 years ago
parent
commit
2d53ba2c69
  1. 6
      bitcoin-qt.pro

6
bitcoin-qt.pro

@ -33,11 +33,13 @@ contains(RELEASE, 1) {
!win32 { !win32 {
# for extra security against potential buffer overflows: enable GCCs Stack Smashing Protection # for extra security against potential buffer overflows: enable GCCs Stack Smashing Protection
QMAKE_CXXFLAGS *= -fstack-protector-all --param ssp-buffer-size=1 QMAKE_CXXFLAGS *= -fstack-protector-all
QMAKE_LFLAGS *= -fstack-protector-all --param ssp-buffer-size=1 QMAKE_LFLAGS *= -fstack-protector-all
# We need to exclude this for Windows cross compile with MinGW 4.2.x, as it will result in a non-working executable! # We need to exclude this for Windows cross compile with MinGW 4.2.x, as it will result in a non-working executable!
# This can be enabled for Windows, when we switch to MinGW >= 4.4.x. # This can be enabled for Windows, when we switch to MinGW >= 4.4.x.
} }
# for extra security (see: https://wiki.debian.org/Hardening)
QMAKE_CXXFLAGS *= -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now
# for extra security on Windows: enable ASLR and DEP via GCC linker flags # for extra security on Windows: enable ASLR and DEP via GCC linker flags
win32:QMAKE_LFLAGS *= -Wl,--dynamicbase -Wl,--nxcompat win32:QMAKE_LFLAGS *= -Wl,--dynamicbase -Wl,--nxcompat

Loading…
Cancel
Save