bc2c2ef8fc5bd1124a794b0de612b1f12321374b |
|
28-Feb-2018 |
Aki Tuomi <aki.tuomi@dovecot.fi> |
m4: Use -U and -D in cc_fortify
Not just -D. This is to test the same thing
that gets used. |
7e86d6308f3f4226c3ed42052cbeb11749821bc2 |
|
28-Feb-2018 |
Aki Tuomi <aki.tuomi@dovecot.fi> |
m4: Remove pthread from tests |
ed97ec6905f3d024058a7c3643358a1b807be243 |
|
21-Dec-2017 |
Timo Sirainen <timo.sirainen@dovecot.fi> |
m4: Avoid _FORTIFY_SOURCE redefinition warnings
Some source based distros like Gentoo already enable -D_FORTIFY_SOURCE=2
by default resulting in the following warnings during build:
<command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined
<built-in>: note: this is the location of the previous definition
Patch by Eray Aslan |
fdf3e1e28e824a562b895c8c6b5d77d70146d357 |
|
12-Sep-2016 |
Josef 'Jeff' Sipek <jeff.sipek@dovecot.fi> |
configure: hardening logic is backwards
Before this change, the argument parsing was busted. The --help string only
compounded the incorrect behavior by suggesting that --disable-hardening
could take a yes/no argument.
| before | after
------------------------------+----------+--------
<no option> | enable | enable
--enable-hardening | disable | enable
--enable-hardening=yes | disable | enable
--enable-hardening=no | enable | disable
--disable-hardening | enable | disable
--disable-hardening=yes | error | error
--disable-hardening=no | error | error |
14a7cd46677cc0052319f2cd84a7b720efa60499 |
|
06-Jul-2016 |
Aki Tuomi <aki.tuomi@dovecot.fi> |
configure: Check for hardening flags |