dbeb43e976
The `tar` implementation in Busybox 1.28.0 and 1.28.1 won't extract a rootfs with some symlinks that appear to look "dangerous". This completely (and silently!) breaks on-target updates via RAUC for me, for example. In the meanwhile, upstream already reverted the commit in question (in their commit a84db18fc71d09e801df0ebca048d82e90b32c6a), so this patch simply applies that revert in Buildroot. The fix has not made it to a release, yet. Signed-off-by: Jan Kundrát <jan.kundrat@cesnet.cz> Bug: https://bugs.busybox.net/show_bug.cgi?id=8411 Bug: https://github.com/rauc/rauc/issues/249 Signed-off-by: Peter Korsgaard <peter@korsgaard.com> |
||
---|---|---|
.. | ||
0001-networking-libiproute-use-linux-if_packet.h-instead-.patch | ||
0002-Makefile.flags-strip-non-l-arguments-returned-by-pkg.patch | ||
0003-tar-unzip-postpone-creation-of-symlinks-with-suspici.patch | ||
busybox-minimal.config | ||
busybox.config | ||
busybox.hash | ||
busybox.mk | ||
Config.in | ||
inittab | ||
mdev.conf | ||
S01logging | ||
S10mdev | ||
S15watchdog | ||
S50telnet | ||
udhcpc.script |