Makefile: install lightning-downgrade.
What changed, and why it matters
This is a packaging/build fix, not a security vulnerability. The `lightning-downgrade` utility was being compiled but accidentally left out of the list of programs installed by `make install`. As a result, official release archives contained the tool's manual page but not the tool itself, meaning users who installed from a release binary could not easily downgrade their node without compiling the tool from source. The patch adds the missing program to the install list so it ships with releases. There is no exploit or code flaw in the software's runtime behavior.
No security action required. Treat as a normal build/packaging fix. If reviewing for release integrity, verify that `make install` and release archive generation now include `tools/lightning-downgrade`.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies Makefile to add tools/lightning-downgrade to BIN_PROGRAMS, alongside tools/lightning-hsmtool. This variable controls which binaries are copied to bindir during make install and therefore which binaries appear in release archives. The change is a one-line addition with no functional code changes to lightning-downgrade or any other component. It resolves issue #9746, a user-reported packaging omission.
Changed components
Makefiletools/lightning-downgrade packaging/installationInspect captured patch +1 / −0
### Makefile
@@ -479,6 +479,7 @@ BIN_PROGRAMS = \
cli/lightning-cli \
lightningd/lightningd \
tools/lightning-hsmtool\
+ tools/lightning-downgrade\
tools/reckless
PKGLIBEXEC_PROGRAMS = \
lightningd/lightning_channeld \Why this scored 23/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.