Zen browser security updates depend on the BOS repo #69
No reviewers
Labels
No labels
P0
P1
P2
P3
audio
bakery
boot
breadbug
bug
build
ci
dependencies
design
disk
docs
encryption
final
firewall
graphics
hardware
idle
installer
keybinds
nvidia
packages
phase-1
polish
recovery
reliability
reproducibility
secure-boot
security
shell
signing
snapshots
supply-chain
swap
tech-debt
theming
ux
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Breadway/bos!69
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/bos-41-zen-browser"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds a SHA-256-pinned
zen-browser-binPKGBUILD and a six-hour watcher for Zen's stable releases. The watcher reads the archive digest from GitHub's Release Asset API and fails closed if the digest is missing, malformed, or differs from the downloaded bytes. A verified build uploads the package and triggers signed-repository publishing. Documents the intended six-hour release-to-repo lag.Verified with a
makepkgbuild of Zen 1.22.3b, an end-to-end watcher run against GitHub's release feed and the live[breadway]database, andscripts/test-ci-verify-zen-release-asset.sh. The test accepted the official release archive at GitHub's published digest0aaee1b3f67f074aebf7fc6c2fe824441bcafd431e9991336479c16370519dd0and rejected a one-byte-modified copy. Shell syntax, workflow YAML parsing, PKGBUILD metadata, andgit diff --checkalso passed. CI reports no statuses for this PR.Closes #41
PR #69 is linked from BOS-41 and ready for independent review. Implementation evidence and acceptance mapping are on the parent issue.
Independent review sent BOS-41 to TODO: new watcher builds use a SHA-256 computed from the downloaded archive itself rather than an independent upstream pin/signature. Rework is requested on feature/bos-41-zen-browser; PR #69 stays open. See BOS-41 for the acceptance mapping and actionable checklist.
Reworked the integrity path on the existing branch. The watcher now reads
digestforzen.linux-x86_64.tar.xzfrom GitHub's Release Asset API, validates thesha256:format, and compares the downloaded archive against that API value before passing it to makepkg. Missing or mismatched digests stop the job. The regression check accepted the fixed 1.22.3b release asset at0aaee1b3f67f074aebf7fc6c2fe824441bcafd431e9991336479c16370519dd0and rejected a one-byte-modified copy. The branch includes current main; PR #69 remains the only BOS-41 PR.Independent re-review at
c846664013: PASS, ready for maintainer merge. Release Asset API digest is checked against downloaded bytes; missing/malformed/mismatched digest paths fail closed. The altered-archive regression logic passed with a synthetic fixture; could not fetch the real release asset here because github.com DNS resolution is unavailable. No CI statuses are configured, and PR #69 is mergeable. BOS is release-sensitive, so it remains unmerged. Full acceptance mapping is on BOS-41.PR #69 passed independent re-review and merged as
6f323f9f72ae5313cd022f3e71f5a417e66cdf96. No CI statuses are configured for this BOS PR; the reviewer verified the independent digest path and fail-closed validation.