You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
Shield wall: several SlowShield instances working as one, a leader and its followers
(docs/design/shieldwall.md, #34). Run in
production across three regions, on hosts and on Kubernetes with the Helm chart.
Pairing: slowshield wall invite on the leader prints a join string (single use, 10 minutes, --minutes up to
60); a follower started with it (SLOWSHIELD_JOIN) checks the leader's key and asks for a click on Join on its
Shield wall page, or joins by itself with SLOWSHIELD_JOIN_CONFIRM=auto. Every message is signed with the
instances' Ed25519 keys. A follower that has joined ignores a join string, so automation can leave it set
(docs/operations.md).
An instance keeps its role across restarts: a follower syncs with the leader it stored, and only SLOWSHIELD_SHIELDWALL_ROLE=standalone takes an instance out of the shield wall.
The leader's overview, security timeline and CSV cover every instance, and narrow to one instance (the leader
included), a location or a label. Followers report their statistics and events exactly once, including their
history at pairing and what they queued while the leader was away.
The leader's Shield wall page lists every instance with its location, labels, version and last contact, and what
each served in the last 24 hours: installs, packages, data, and how much came from its own cache, through the
leader, or from the registries.
Followers take the leader's policy and blocks: stricter settings at once, looser ones after an hour and never
below SLOWSHIELD_SHIELDWALL_MIN_DELAY_DAYS (1 day); a block the leader lifts stays a day. Their own stricter
settings and their own exceptions stay in force. Takedowns, tamper flags, tag history and Maven, Cargo and NuGet
listing times come down too, with the leader's observation times bounded by how recently the follower synced.
Package files come through the leader's cache when it is up (SLOWSHIELD_SHIELDWALL_VIA_LEADER), checked by the
follower as always, so the wall downloads each file from the registries once; a follower that can't reach its
leader works on its own.
The leader compares every follower's first fingerprint of a file with its own; a follower that saw different
bytes refuses the file, and the leader records it. A follower's fingerprint only ever refuses a file on that
follower, and one that names another package or version than the leader's record of the file is refused.
A follower must trust its leader's certificate, and the shipped stacks default to Caddy's private CA: Helm shieldwall.leaderCaSecret (the chart refuses a follower without it, unless shieldwall.leaderPubliclyTrusted),
Compose LEADER_CA_SECRET_FILE. A follower that lacks it says so on its Shield wall page.
The leader sends fail_open for every ecosystem it has. A follower skips the settings for an ecosystem it
doesn't know, with a warning that names it, and applies the rest of the policy.
Settings in a follower's own config count against its leader's policy (stricter wins), so the shipped configs
leave default_delay_days, enforce_age_on_download and fail_open commented out.
One Tailscale Service name for many instances, on hosts (tailscale serve --service) and on Kubernetes, and a Helm
follower of a leader that is only on a tailnet: docs/tailscale.md, with example manifests in deploy/helm/slowshield/examples.