Skip to content

build: publish FreeBSD binaries - #11

Merged
Quick104 merged 1 commit into
mainfrom
build/freebsd-binaries
Nov 17, 2026
Merged

Quick104 merged 1 commit into
mainfrom
build/freebsd-binaries

Conversation

@Quick104

@Quick104 Quick104 commented Nov 17, 2026 •

Copy link
Copy Markdown
Collaborator

Problem

Related issue: N/A — narrow fix

A Silo server running on FreeBSD can't install this plugin. Releases ship Linux and macOS binaries only, and manifest.json lists only those platforms, so the server doesn't offer the plugin on freebsd/amd64 or freebsd/arm64.

Approach

Add both FreeBSD targets everywhere this repository lists release platforms:

  • manifest.json supported_platforms.
  • scripts/dist.py PLATFORMS, so make dist builds, packages, and verifies a ZIP archive for each. verify_binary gains a FreeBSD branch that checks the ELF machine type and the OS/ABI byte (Go writes 9, FreeBSD), so a FreeBSD archive can't carry a Linux binary.
  • .github/workflows/release.yml: the loop that extracts the raw plugin-<os>-<arch> binaries and adds them to checksums.txt, the signing job's expected subject list, and the release's file list. The archives and checksums reach the attestation, bundle verification, and catalog dispatch steps through checksums.txt, so those steps need no other change.
  • docs/DEVELOPMENT.md, which lists the archives dist/ contains.

version goes from 0.2.3 to 0.2.4 in manifest.json and in the Makefile VERSION default, as the release section of docs/DEVELOPMENT.md requires.

No plugin code changes. With the repository's adapted Tailscale source (make prepare), the plugin and its embedded tsnet node compile and vet for both FreeBSD targets with CGO_ENABLED=0.

Once 0.2.4 is released and the community catalog picks it up, a FreeBSD server admin sees the plugin in the catalog and can install it, or download the FreeBSD ZIP from the release.

Validation

Toolchain: Go 1.27.4, Python 3 (darwin/arm64 host).

Before editing, on main after make prepare, with the Makefile's GOFLAGS:

$ GOOS=freebsd GOARCH=amd64 CGO_ENABLED=0 go build -trimpath -o plugin .   # ok
$ GOOS=freebsd GOARCH=amd64 CGO_ENABLED=0 go vet ./...                     # ok
$ GOOS=freebsd GOARCH=arm64 CGO_ENABLED=0 go build -trimpath -o plugin .   # ok
$ GOOS=freebsd GOARCH=arm64 CGO_ENABLED=0 go vet ./...                     # ok

After the change, the CI gate:

$ make check
Ran 7 tests in 0.013s
OK
ok  	github.com/Silo-Community/silo-plugin-tailscale	14.351s
ok  	github.com/Silo-Community/silo-plugin-tailscale/internal/tailscale	21.889s
ok  	tailscale.com/feature/acme	1.277s
(go vet and gofmt check pass)

$ make audit
Your code may be affected by 0 vulnerabilities.

$ make dist; cp dist/checksums.txt first.txt; make dist; cmp first.txt dist/checksums.txt   # identical
silo-plugin-tailscale-0.2.4-linux-amd64.zip
silo-plugin-tailscale-0.2.4-linux-arm64.zip
silo-plugin-tailscale-0.2.4-darwin-arm64.zip
silo-plugin-tailscale-0.2.4-freebsd-amd64.zip
silo-plugin-tailscale-0.2.4-freebsd-arm64.zip

file reports the plugin in each FreeBSD archive as a statically linked FreeBSD ELF executable (x86-64 and aarch64), and each archive's manifest lists all five platforms. I also ran the release workflow's "Prepare release assets" loop and the signing job's subject-list comparison by hand against that dist/: the subject list matches all 10 assets. verify_binary accepts both FreeBSD binaries and rejects a Linux binary and a wrong-architecture FreeBSD binary.

The FreeBSD binaries are cross-compiled only; nobody on the project ran them on a FreeBSD host. The real-tailnet checks listed under "Validation scope" in docs/DEVELOPMENT.md were not run on FreeBSD.

Evidence: https://evidence.siloserver.org/r/silo-plugin-tailscale/freebsd-binaries/

Risks

Existing platforms build as before. On FreeBSD, the plugin's tsnet node is untested at runtime: enrollment, certificates, and the listeners have only been compiled for FreeBSD. Releases get two more archives and two more raw binaries.

Other clients: N/A (no client-visible change)

Checklist

  • I read and can explain the complete diff.
  • This pull request addresses one concern.

AI Disclosure

  • Harness: Claude Code
  • Tool(s): Claude Code
  • Model(s): claude-opus-5-5
  • Involvement: Fully AI-generated; requested by the project owner, not yet human verified
  • Adversarial review: n/a; a build-matrix and release-packaging change with no plugin code changes

🤖 Generated with Claude Code

Build, verify, sign, and publish freebsd/amd64 and freebsd/arm64
archives and raw binaries alongside the existing targets. dist.py checks
the ELF OS/ABI byte so a FreeBSD archive cannot hold a Linux binary.
Raise the version to 0.2.4 in manifest.json and the Makefile so the
merge commit is the taggable release commit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Quick104
Quick104 merged commit 76e176b into main Nov 17, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant