fortify-headers - Standalone portable header-based implementation of FORTIFY

Age	Commit message (Collapse)	Author
2015-06-25	Add __extension__ mark to include_next to silence -pedantic	Steven Barth
	Signed-off-by: Steven Barth <steven@midlink.org>
2015-06-03	Use namespace-safe macro, param and variable names	Trutz Behn

2015-05-13	Add LICENSE header	sin

2015-05-13	Add fortify_fn() helper in fortify-headers.h	sin

2015-05-07	Minor style fix	sin

2015-05-07	fix realpath when stdlib.h is included before limits.h	Natanael Copa
	If program includes stdlib.h before limits.h without _XOPEN_SOURCE, _GNU_SOURCE or _BSD_SOURCE explicitly set, then will it always trigger the trap with musl libc. This is becase stdlib.h will pull in features.h which will set _GNU_SOURCE. This means that the fortify stdlib.h will not include limits.h but it will still trigger the fortified realpath(), but without PATH_MAX set. We fix this by including system stdlib.h before testing if limits.h should be included. Since PATH_MAX is known at compile time we can also error at compile time, instead of compiling a broken realpath().
2015-03-14	Use __typeof__ to in part avoid replicating function types	Trutz Behn

2015-03-14	Add __artificial__ to aid in debugging	sin

2015-03-13	Restore C++ support	sin

2015-03-13	Rework fortify implementation to use extern inline	sin
	Overriding functions with macros is legal in C but a lot of software is not prepared for it. Use the extern inline method to achieve the same result.
2015-03-11	Put include guards in the reserved namespace	Trutz Behn
	fortify-headers is considered part of the implementation.
2015-03-11	Ignore C++ for now	sin
	It is not legal to override standard functions using macros in C++. We may have to revisit this in the future.
2015-03-11	Add ifdef guards for C++ code	sin

2015-02-28	Style fix	sin

2015-02-28	__fortify_realpath() should trap if PATH_MAX is not defined	sin
	This is currently done only if the pointer is non-NULL.
2015-02-24	Add realpath() check	sin