Add hardened Flea package to fast ring - #288
Merged
Merged
Conversation
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
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.
What this does
Adds Flea 0.1.2 to the fast ring as a source-built, x86_64 package. It installs the binary, desktop entry, icon, QML UI, and Omarchy QML links.
Security review
The published v0.1.2 tag was not safe to ship as-is. It had four blocking issues that are already fixed on the upstream hardening branch:
bwraporprlimitis unavailableThe PKGBUILD applies those four exact upstream patches from thisisgm/flea#2, with every source pinned by SHA-256. Future releases are rejected unless all four security invariants are present.
After applying the patches:
No blocking findings remain in the packaged result. Recursive file operations still have low-impact, same-user path races; Flea does not cross a privilege boundary.
Upstream sync
Adds a strict GitHub Releases sync hook with the normal 24-hour quarantine. Since upstream does not publish a checksum manifest, the hook hashes the release tarball itself. It only emits an update after validating the archive structure and the four required security fixes.
Validation
makepkgbuild and source verificationFlea is x86_64-only for now because upstream's aarch64 build is currently broken: thisisgm/flea#13.