chore: weekly upstream bumps (2026-08-24) - #6
Merged
Conversation
The 8.21.0 bump shipped a curl that was dynamically linked against libssl.so.3/libcrypto.so.3 (musl PIE), despite the "clean static link" intent. file(1) misreported it as static only because UPX had stripped the section headers. Cause: libtool swallows a plain LDFLAGS=-static and links the exe dynamically. Fix uses libtool's own curl_LDFLAGS=-all-static, moves LDFLAGS=-static to configure, and adds PKG_CONFIG=--static so OpenSSL 3's private transitive deps resolve. Rebuilt x64/curl is now a genuine static binary (no NEEDED entries, runs standalone: curl 8.21.0 ... OpenSSL/3.3.7). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The dropbear ARM binaries shipped unstripped, carrying debug_info, and
UPX-unpacked. Root cause was in scripts/gen_dockerfiles.py: the pack
step ran the host x86_64 strip over ARM ELF too, which errors with
"Unable to recognise the format". Because strip and upx shared one
trailing "|| echo upx failed", that error was both swallowed and
short-circuited the whole && chain, so upx never ran, leaving even the
x64 binaries unpacked.
Fix _collect_and_pack to:
- strip x64 with host strip, ARM with arm-linux-musleabihf-strip
- skip strip for Go (already linked -s -w)
- wrap upx in a subshell so its || guards only upx, letting a real
strip failure abort the build instead of hiding it
Rebuilt dropbear: all 10 binaries now stripped and UPX-packed (arm
~3x smaller), integrity verified with upx -t. Regenerated the curl,
tmux, dropbear, es-dump Dockerfiles from the updated generator.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated weekly upstream bump.
Each binary was rebuilt from source in its Dockerfile
(build//Dockerfile) and smoke-tested before landing here.
Packaging per binary:
-s -w(already stripped); UPXdeclines to pack it, so it ships static-stripped but unpacked.
Follow-up fixes on this branch
Review of the first push caught two build defects, now fixed:
libssl.so.3/libcrypto.so.3(filemisreported it as staticbecause UPX had stripped the section headers) and failed to run
without those libs. libtool swallows a plain
LDFLAGS=-static;fixed with
curl_LDFLAGS=-all-static+PKG_CONFIG="pkg-config --static". Rebuilt curl is genuinely static (0 NEEDED, runsstandalone:
curl 8.21.0 ... OpenSSL/3.3.7).the host x86_64
stripover ARM ELF, which errored and (via a shared|| echotail) silently skipped UPX for x64 too. Fixed to strip ARMwith
arm-linux-musleabihf-stripand isolate the tolerant UPX step.All 10 dropbear binaries are now stripped + packed (
upx -tOK).Reviewer checklist:
./scripts/build.sh <tool> --extract)