Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2 |
|
#
0302f53e |
| 16-Apr-2019 |
Sascha Wildner <saw@online.de> |
libc: Fix some more -Wmissing-prototypes warnings.
|
Revision tags: v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc |
|
#
7adf0194 |
| 11-Sep-2015 |
John Marino <draco@marino.st> |
libc: Add stack protector support back
Based on regressions indicated by dports bulk build (< 10), it appears that the deactivated stack_protector.c code was used with static stack protection (e.g.
libc: Add stack protector support back
Based on regressions indicated by dports bulk build (< 10), it appears that the deactivated stack_protector.c code was used with static stack protection (e.g. -lssp_nonshared).
FreeBSD moved the file to its own area less than a month ago, which is why I thought it had been removed. The plan is to put all security related code in the same area, so I'm going to follow suit. While here, remove the stack_smash_handler, which I believe is obsolete, and reduce differences with FreeBSD.
show more ...
|