fortify-headers/tests, branch 2.3.2Standalone portable header-based implementation of FORTIFY_SOURCE=3
http://git.dustri.org/fortify-headers/atom?h=2.3.22024-10-09T23:51:34ZDisable snprintf/sprintf hardening for now2024-10-09T23:51:34Zjvoisin2024-10-09T23:20:07Zurn:sha1:c3b48c6b0bf501802295c85b1cf54275d6b74883Run various C versions in the CI2024-10-08T13:21:13Zjvoisin2024-10-08T01:51:44Zurn:sha1:f8155f0b945c5cfb3600d7c146a5d86870ed09d2Work around a gcc warning2024-09-06T11:38:22Zjvoisin2024-09-06T11:36:15Zurn:sha1:f2e7f24daaa43c0927130b6ed02c3ed17689b3ca
It seems that annotating sprintf with `write` makes gcc unhappy, as its
analyser is unable to understand that we're checking if `__b != -1` before
calling `__orig_snprintf`, so let's comment this annotation for now.
prefix special defines with FORTIFY_2024-07-10T13:20:23Zpsykose2024-07-10T04:49:02Zurn:sha1:459d202b1bbf7abb817a596ce9374edfb7b4da8f
just in case, and because 'PEDANTIC_CHECKS' is a really generic name
Add a test for C++ compilation2024-06-21T14:40:26Zjvoisin2024-06-21T14:25:40Zurn:sha1:8f8e5c1a7854f05bfa94fc41033706bc14682223Fix some pointer-arithmetic warnings2024-06-15T13:46:35Zjvoisin2024-06-14T17:46:14Zurn:sha1:520e7e4a631cc038b3e867b2255235da35a98ece
This should fix the second part of #59
Add vasprintf/asprintf2024-05-26T20:19:27Zjvoisin2024-05-20T12:48:35Zurn:sha1:1becad43298e74ba73bc66f9d44523e5d121c667
The only hardening being done here is to set the char** parameter to thos
functions to NULL in case of an error, to prevent it from being used should
people forget to check return values. This is already done on some BSD, as well
as in Rocky Linux.
Add a test2024-04-24T16:40:13Zjvoisin2024-04-24T16:36:10Zurn:sha1:3375426d8c18f43f58ab83c261735b04562828aeFix some overlap mismatch2024-04-24T15:14:46Zjvoisin2024-04-24T15:09:08Zurn:sha1:a817e1555a755224cacc1cbdeeaefb6a1de606f0
This was caught by the following test:
```
int main(void) {
char c[32];
memcpy(c, c + 16, 16);
}
```
Reported-by: q66
Disable pedantic checks by default2024-04-24T12:51:19Zjvoisin2024-04-24T12:49:52Zurn:sha1:265fa03fa0c467c9c41d803ebe2a538e758cba20
They can be re-enabled via `PEDANTIC_CHECKS`