<feed xmlns='http://www.w3.org/2005/Atom'>
<title>busybox-w32/scripts, branch long_paths</title>
<subtitle>A mirror of https://github.com/rmyorston/busybox-w32.git
</subtitle>
<id>https://git.lua4.win/busybox-w32/atom?h=long_paths</id>
<link rel='self' href='https://git.lua4.win/busybox-w32/atom?h=long_paths'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/'/>
<updated>2025-12-29T13:57:05+00:00</updated>
<entry>
<title>win32: wcwidth_alt.c: new generator script, re-generate code</title>
<updated>2025-12-29T13:57:05+00:00</updated>
<author>
<name>Avi Halachmi (:avih)</name>
<email>avihpit@yahoo.com</email>
</author>
<published>2025-12-25T22:02:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=6f847c296bf94401c0c147bf3c5aa1e8531b9dbf'/>
<id>urn:sha1:6f847c296bf94401c0c147bf3c5aa1e8531b9dbf</id>
<content type='text'>
Previously, scripts/mkwcwidth generated a wcwidth implementation based
on input from the python wcwidth: https://github.com/jquast/wcwidth .

However, that project is not updated frequently, and the less
dependencies - the better.

This new script instead prints an implementation based directly on the
original Unicode files - which it can also download.

It generates the same code as before (same data structures, etc).

It was then used to re-generate libbb/wcwidth_alt.c, as follows:

  ./scripts/mkwcwidth DL=15.1.0 FAST_FUNC &gt; libbb/wcwidth_alt.c

This is the same Unicode version as the previous file, just to make
the codepoint differences visible easily.

These differences are very small, and the script itself explains where
and why it differs from https://github.com/jquast/wcwidth .

Next commits will update the tables to the latest unicode version.
</content>
</entry>
<entry>
<title>Use Windows library for cryptographic checksums</title>
<updated>2025-06-09T12:23:49+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2025-06-09T12:23:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=596c443112d09506c3bf13ac98046a84b912e56c'/>
<id>urn:sha1:596c443112d09506c3bf13ac98046a84b912e56c</id>
<content type='text'>
Add a new feature to libbb, FEATURE_USE_CNG_API, which enables the
use of the Cryptography API: Next Generation library to calculate
checksums.  It is disabled by default except in the mingw64u default
config, as the API requires Windows 10+ to function.  Usage of this
API provides a size benefit and delegates hardware optimizations to
the operating system cryptography library.

Based on GitHub PR #498 by rfl890.

Saves 4064 bytes in the mingw64u case.
</content>
</entry>
<entry>
<title>Merge branch 'busybox' into merge</title>
<updated>2025-05-19T07:34:32+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2025-05-19T07:34:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=64bf69893bd99c305d13a956389f216e7d15c682'/>
<id>urn:sha1:64bf69893bd99c305d13a956389f216e7d15c682</id>
<content type='text'>
</content>
</entry>
<entry>
<title>archival: disallow path traversals (CVE-2023-39810)</title>
<updated>2025-04-16T01:03:17+00:00</updated>
<author>
<name>Denys Vlasenko</name>
<email>vda.linux@googlemail.com</email>
</author>
<published>2024-10-02T08:12:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=9a8796436b9b0641e13480811902ea2ac57881d3'/>
<id>urn:sha1:9a8796436b9b0641e13480811902ea2ac57881d3</id>
<content type='text'>
Create new configure option for archival/libarchive based extractions to
disallow path traversals.
As this is a paranoid option and might introduce backward
incompatibility, default it to no.

Fixes: CVE-2023-39810

Based on the patch by Peter Kaestle &lt;peter.kaestle@nokia.com&gt;

function                                             old     new   delta
data_extract_all                                     921     945     +24
strip_unsafe_prefix                                  101     102      +1
------------------------------------------------------------------------------
(add/remove: 0/0 grow/shrink: 2/0 up/down: 25/0)               Total: 25 bytes

Signed-off-by: Denys Vlasenko &lt;vda.linux@googlemail.com&gt;
</content>
</entry>
<entry>
<title>Update PDCurses</title>
<updated>2025-04-10T18:41:43+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2025-04-10T18:41:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=486c1fcc341472fd8d64b820c3a7934cf3f42132'/>
<id>urn:sha1:486c1fcc341472fd8d64b820c3a7934cf3f42132</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'busybox' into merge</title>
<updated>2024-09-28T07:13:32+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2024-09-28T07:13:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=431e2704c17d5c0e51a0cbebfb1105bd4962b3f7'/>
<id>urn:sha1:431e2704c17d5c0e51a0cbebfb1105bd4962b3f7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>fixdep: add fstat error handling</title>
<updated>2024-09-27T18:03:30+00:00</updated>
<author>
<name>Sam James</name>
<email>sam@gentoo.org</email>
</author>
<published>2024-04-23T20:10:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=480a07bd6828285628abbbe3fe8e5e3b25ce1a92'/>
<id>urn:sha1:480a07bd6828285628abbbe3fe8e5e3b25ce1a92</id>
<content type='text'>
When `fstat` fails, `st` is left uninitialised. In our case, Ben Kohler
noticed our release media builds were failing in Gentoo on x86 when building
busybox with occasional SIGBUS. This turned out to be EOVERFLOW (from 32-bit
ino_t) which wasn't being reported because nothing was checking the return value
from `fstat`.

Fix that to avoid UB (use of uninit var) and to give a more friendly
error to the user.

This actually turns out to be fixed already in the kernel from back in
2010 [0] and 2016 [1].

[0] https://github.com/torvalds/linux/commit/a3ba81131aca243bfecfa78c42edec0cd69f72d6
[1] https://github.com/torvalds/linux/commit/46fe94ad18aa7ce6b3dad8c035fb538942020f2b

Reported-by: Ben Kohler &lt;bkohler@gentoo.org&gt;
Signed-off-by: Sam James &lt;sam@gentoo.org&gt;
Signed-off-by: Denys Vlasenko &lt;vda.linux@googlemail.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'busybox' into merge</title>
<updated>2024-06-23T08:44:03+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2024-06-23T08:35:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=b07c177b446498ccd739b367f9e80337c3dfa55a'/>
<id>urn:sha1:b07c177b446498ccd739b367f9e80337c3dfa55a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>build system: fix ncurses detection</title>
<updated>2024-04-28T14:48:03+00:00</updated>
<author>
<name>Ron Yorston</name>
<email>rmy@pobox.com</email>
</author>
<published>2024-04-28T14:48:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=e21f531c297d1567720c8b0f1c9bab7daf0cfdad'/>
<id>urn:sha1:e21f531c297d1567720c8b0f1c9bab7daf0cfdad</id>
<content type='text'>
Recent versions of gcc fail to build the binary to test for
ncurses because main() is lacking a return type.
</content>
</entry>
<entry>
<title>docproc: avoid segfault during file closing</title>
<updated>2024-04-13T15:57:46+00:00</updated>
<author>
<name>Yan Zhu</name>
<email>zhuyan2015@foxmail.com</email>
</author>
<published>2023-09-11T16:03:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/busybox-w32/commit/?id=681e4f5d922b9f0ea968238750d5c5d748eac809'/>
<id>urn:sha1:681e4f5d922b9f0ea968238750d5c5d748eac809</id>
<content type='text'>
In the function find_export_symbols, since the fopen file does not
exit when it fails, there is a dereference problem in fclose(fp),
which will cause a segmentation fault.

Signed-off-by: Yan Zhu &lt;zhuyan2015@foxmail.com&gt;
Signed-off-by: Denys Vlasenko &lt;vda.linux@googlemail.com&gt;
</content>
</entry>
</feed>
