fortify-headers, branch 2.3.1Standalone portable header-based implementation of FORTIFY_SOURCE=3
http://git.dustri.org/fortify-headers/atom?h=2.3.12024-07-02T13:40:44ZUpdate a bit the readme2024-07-02T13:40:44Zjvoisin2024-07-02T13:40:44Zurn:sha1:936d55d4c263264bc21ccdaeed2537ff0d4320f2Add 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
Remove `restrict` keywords2024-06-14T17:37:48Zjvoisin2024-06-14T17:37:48Zurn:sha1:6939e3382a232d20882c1c7e74274132de154bb6
- They're not used anywhere else in fortify-headers
- It's breaking compilation on C++, because compatibility is hard
It was initially reported on https://gitlab.alpinelinux.org/alpine/aports/-/issues/16200
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.
Improve the testsuite reliability wrt. gcc2024-05-20T08:22:46Zjvoisin2024-05-20T07:38:42Zurn:sha1:92c611ad8abb146ed548301de8bc011c2b17bccdAdd 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`
Relax our checks for memchr on C11 and above2024-03-19T17:35:13Zjvoisin2024-03-19T17:35:13Zurn:sha1:8ed72e7c1caa0eb4238e649063c26a11720935de
Since C11:
> This function behaves as if it reads the bytes sequentially and stops as soon
as a matching bytes is found: if the array pointed to by ptr is smaller than
count, but the match is found within the array, the behavior is well-defined.
Reported-by: q66