<feed xmlns='http://www.w3.org/2005/Atom'>
<title>fortify-headers/include, branch 2.3.2</title>
<subtitle>Standalone portable header-based implementation of FORTIFY_SOURCE=3 
</subtitle>
<id>http://git.dustri.org/fortify-headers/atom?h=2.3.2</id>
<link rel='self' href='http://git.dustri.org/fortify-headers/atom?h=2.3.2'/>
<link rel='alternate' type='text/html' href='http://git.dustri.org/fortify-headers/'/>
<updated>2024-10-09T23:51:34Z</updated>
<entry>
<title>Disable snprintf/sprintf hardening for now</title>
<updated>2024-10-09T23:51:34Z</updated>
<author>
<name>jvoisin</name>
</author>
<published>2024-10-09T23:20:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dustri.org/fortify-headers/commit/?id=c3b48c6b0bf501802295c85b1cf54275d6b74883'/>
<id>urn:sha1:c3b48c6b0bf501802295c85b1cf54275d6b74883</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix usage of strnlen</title>
<updated>2024-10-03T22:16:50Z</updated>
<author>
<name>Quentin Rameau</name>
</author>
<published>2024-10-02T19:15:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dustri.org/fortify-headers/commit/?id=6573631a5e4339a2fc2f86680e36e35e25bf416c'/>
<id>urn:sha1:6573631a5e4339a2fc2f86680e36e35e25bf416c</id>
<content type='text'>
As with previous commit, some strnlen calls
where introduced in 22a8094, but not reverted.

As strnlen isn't part of C standard,
this was breaking C builds.
</content>
</entry>
<entry>
<title>Use const fd_set for FD_ISSET</title>
<updated>2024-10-03T18:22:48Z</updated>
<author>
<name>Natanael Copa</name>
</author>
<published>2024-10-03T08:56:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dustri.org/fortify-headers/commit/?id=60202fb5b50f3e56bf82f3424360377a29e25709'/>
<id>urn:sha1:60202fb5b50f3e56bf82f3424360377a29e25709</id>
<content type='text'>
This fixes invalid conversion errors when the fd_set is defined as
const.

fixes https://github.com/jvoisin/fortify-headers/issues/66
</content>
</entry>
<entry>
<title>Work around a gcc warning</title>
<updated>2024-09-06T11:38:22Z</updated>
<author>
<name>jvoisin</name>
</author>
<published>2024-09-06T11:36:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dustri.org/fortify-headers/commit/?id=f2e7f24daaa43c0927130b6ed02c3ed17689b3ca'/>
<id>urn:sha1:f2e7f24daaa43c0927130b6ed02c3ed17689b3ca</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Revert d2594298b89d0fb8989cae3ebc8900e77b6aa478</title>
<updated>2024-09-02T14:11:06Z</updated>
<author>
<name>jvoisin</name>
</author>
<published>2024-09-02T14:08:38Z</published>
<link rel='alternate' type='text/html' href='http://git.dustri.org/fortify-headers/commit/?id=114b563adc2b942bc5abd4c5820507076d453f64'/>
<id>urn:sha1:114b563adc2b942bc5abd4c5820507076d453f64</id>
<content type='text'>
As reported on irc:

```
17:51 &lt;q&gt; jvoisin, fortify-headers seems to be broken (on Alpine at least)
17:52 &lt;q&gt; Repeating the message from over-there:
17:52 &lt;q&gt; /usr/include/fortify/string.h: In function 'strncat':
17:52 &lt;q&gt; /usr/include/fortify/string.h:297:36: error: implicit declaration of function 'strnlen'; did you mean 'strlen'? [-Wimplicit-function-declaration]
17:52 &lt;q&gt; This is with a simple file that includes string.h and call strncat, built with c99 -O1 f.c
```
</content>
</entry>
<entry>
<title>Fix access annotation for stpncpy/strncpy</title>
<updated>2024-07-10T14:46:15Z</updated>
<author>
<name>jvoisin</name>
</author>
<published>2024-07-10T14:46:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dustri.org/fortify-headers/commit/?id=c4d9299abf7f6b941493fc487d2ccbb47d756479'/>
<id>urn:sha1:c4d9299abf7f6b941493fc487d2ccbb47d756479</id>
<content type='text'>
The dsize parameter is the length of the dst,
not the length of the src.

Reported-by: ncopa
</content>
</entry>
<entry>
<title>Fix access annotations to snprintf/sprintf</title>
<updated>2024-07-10T14:03:42Z</updated>
<author>
<name>jvoisin</name>
</author>
<published>2024-07-10T14:03:42Z</published>
<link rel='alternate' type='text/html' href='http://git.dustri.org/fortify-headers/commit/?id=9014b0266147dbb74d5d9e6e2c24ae9d21ad7e07'/>
<id>urn:sha1:9014b0266147dbb74d5d9e6e2c24ae9d21ad7e07</id>
<content type='text'>
In the same spirit as the previous commit.

Reported-by: ncopa
</content>
</entry>
<entry>
<title>Fix `access` annotations for vsnprintf/vsprintf</title>
<updated>2024-07-10T13:49:00Z</updated>
<author>
<name>jvoisin</name>
</author>
<published>2024-07-10T13:49:00Z</published>
<link rel='alternate' type='text/html' href='http://git.dustri.org/fortify-headers/commit/?id=6f5423255b6d78b0d6979e6319642ae530f3e2b7'/>
<id>urn:sha1:6f5423255b6d78b0d6979e6319642ae530f3e2b7</id>
<content type='text'>
This fix the following issue:

```
In file included from exec-cmd.c:9:
In function 'vsnprintf',
    inlined from 'report.constprop' at subcmd-util.h:13:2:
/usr/include/fortify/stdio.h:162:16: error: 'msg' may be used uninitialized [-Werror=maybe-uninitialized]
  162 |         return __orig_vsnprintf(__s, __n, __f, __v);
      |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/fortify/strings.h:23,
                 from /usr/include/string.h:59,
                 from /usr/include/fortify/string.h:23,
                 from /home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/include/linux/string.h:6,
                 from exec-cmd.c:3:
/usr/include/fortify/stdio.h: In function 'report.constprop':
/usr/include/fortify/stdio.h:152:1: note: in a call to '__orig_vsnprintf' declared with attribute 'access (read_write, 1, 2)' here
  152 | _FORTIFY_FN(vsnprintf) int vsnprintf(char * _FORTIFY_POS0 __s, size_t __n,
      | ^~~~~~~~~~~
In file included from exec-cmd.c:10:
subcmd-util.h:12:14: note: 'msg' declared here
   12 |         char msg[1024];
      |              ^~~
cc1: all warnings being treated as errors
make[5]: *** [/home/ncopa/aports/main/linux-lts/src/linux-6.6/tools/build/Makefile.build:98: /home/ncopa/aports/main/linux-lts/src/build-virt.x86_64/tools/objtool/libsubcmd/exec-cmd.o] Error 1
make[4]: *** [Makefile:80: /home/ncopa/aports/main/linux-lts/src/build-virt.x86_64/tools/objtool/libsubcmd/libsubcmd-in.o] Error 2
make[3]: *** [Makefile:78: /home/ncopa/aports/main/linux-lts/src/build-virt.x86_64/tools/objtool/libsubcmd/libsubcmd.a] Error 2
make[2]: *** [Makefile:73: objtool] Error 2
make[1]: *** [/home/ncopa/aports/main/linux-lts/src/linux-6.6/Makefile:1362: tools/objtool] Error 2
make: *** [/home/ncopa/aports/main/linux-lts/src/linux-6.6/Makefile:234: __sub-make] Error 2
```

Reported-by: ncopa
</content>
</entry>
<entry>
<title>prefix special defines with FORTIFY_</title>
<updated>2024-07-10T13:20:23Z</updated>
<author>
<name>psykose</name>
</author>
<published>2024-07-10T04:49:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dustri.org/fortify-headers/commit/?id=459d202b1bbf7abb817a596ce9374edfb7b4da8f'/>
<id>urn:sha1:459d202b1bbf7abb817a596ce9374edfb7b4da8f</id>
<content type='text'>
just in case, and because 'PEDANTIC_CHECKS' is a really generic name
</content>
</entry>
<entry>
<title>Fix some pointer-arithmetic warnings</title>
<updated>2024-06-15T13:46:35Z</updated>
<author>
<name>jvoisin</name>
</author>
<published>2024-06-14T17:46:14Z</published>
<link rel='alternate' type='text/html' href='http://git.dustri.org/fortify-headers/commit/?id=520e7e4a631cc038b3e867b2255235da35a98ece'/>
<id>urn:sha1:520e7e4a631cc038b3e867b2255235da35a98ece</id>
<content type='text'>
This should fix the second part of #59
</content>
</entry>
</feed>
