Repository navigation
A security and maintenance release: fewer dependencies, no known vulnerabilities, and releases you can verify.
Simpler install
- No Rust toolchain needed. SD cards are now found with macOS's own
diskutil, using the same rule the BeagleBoard Imaging Utility uses (a physical whole disk that macOS reports as removable or ejectable).tools/setup_bb_imager.shand its ~790 Rust dependencies are gone. Flashing itself is unchanged. - Card builds use an Alpine-based container, built fresh on every run, so its packages are always the current, patched ones. A test build of the same card with the old and new containers produced identical files.
Fixes
- The ColorLight check no longer stops on a controller log line with an unusual or impossible timestamp. These include fractions of a second Python 3.9 can't parse, impossible dates, and Feb 29 read in a non-leap year.
- Saving a malformed fleet policy from the Settings page now shows an error, instead of the request getting no answer.
Security
- No open vulnerabilities at any severity in the card-builder container. The previous Debian-based one carried about 100 that Debian hasn't fixed yet.
- Verifiable releases. Starting with this one, each release includes a source archive and SBOMs (software bills of materials), all signed with build provenance. Check a download with
gh attestation verify FPP-Backup-v0.3.1.tar.gz -R SRipaldi/FPP-Backup. Releases are immutable once published. - CI checks on every change: CodeQL (extended security queries), unit tests on Python 3.9 and 3.13 and on macOS, ShellCheck, hadolint, and fuzzing of the parsers for controller logs, release notes, settings and policies. Weekly scans cover the container's dependencies and the repository's OpenSSF Scorecard. CI uses no third-party GitHub Actions; its tools are pinned by version and SHA-256.
- SECURITY.md now sets out how to report a vulnerability and the response timeline.
tools/check_public.pychecks commits, PRs and releases for an installation's own names and addresses, secrets and personal data before anything is published.--install-hookssets it up for every commit and push.
Upgrading
Pull the new version (or clone --branch v0.3.1) and restart the UI server. You can delete work/bin/bb-imager-cli and work/bb-imager-src/; nothing uses them any more.
Full changes: v0.3.0...v0.3.1