Repository navigation
docs(manual-tests): Record hull on Linux on a network gateway, 2026-11-18 - #674
Merged
Merged
Conversation
…1-18 Brig puts a hull on Linux sandbox on a network gateway since #667, and refuses a policy, a divert and a published port there because no run on a real hull had shown they work. This records one, on a fresh rootless install of brig-standalone-linux v0.1.0-rc22 with Brig from main: the postures, sandbox-to-sandbox reachability, rm --all, and the three refused capabilities driven at hull level with the flags and API calls Brig uses on macOS. All hold. The one refusal is hull's own: an image whose USER is a name. Refs: brig-sh/hull#105 Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
ananos
force-pushed
the
docs/hull-linux-gateway-record
branch
from
November 18, 2026 18:09
f3a2ce3 to
73a3ed3
Compare
5 of 6 tasks
ananos
marked this pull request as ready for review
November 18, 2026 18:33
pmoust
approved these changes
Nov 18, 2026
6 tasks done
ananos
added a commit
that referenced
this pull request
Nov 19, 2026
The runtime now serves a divert, brig.internal and a published port on hull on Linux, so the pages that said it refuses them were wrong. They now put hull on Linux beside hvi: the same gateway, the same diverts and the same API for forwards. The measured run is the record of 2026-11-18, which #674 adds; that pull request merges first, since these pages link its page. Refs: brig-sh/hull#105 Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
ananos
added a commit
that referenced
this pull request
Nov 19, 2026
The runtime now serves a divert, brig.internal and a published port on hull on Linux, so the pages that said it refuses them were wrong. They now put hull on Linux beside hvi: the same gateway, the same diverts and the same API for forwards. The measured run is the record of 2026-11-18, which #674 adds; that pull request merges first, since these pages link its page. Refs: brig-sh/hull#105 Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
ananos
added a commit
that referenced
this pull request
Nov 19, 2026
The runtime now serves a divert, brig.internal and a published port on hull on Linux, so the pages that said it refuses them were wrong. They now put hull on Linux beside hvi: the same gateway, the same diverts and the same API for forwards. The measured run is the record of 2026-11-18, which #674 adds; that pull request merges first, since these pages link its page. Refs: brig-sh/hull#105 Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
ananos
added a commit
that referenced
this pull request
Nov 19, 2026
The runtime now serves a divert, brig.internal and a published port on hull on Linux, so the pages that said it refuses them were wrong. They now put hull on Linux beside hvi: the same gateway, the same diverts and the same API for forwards. The measured run is the record of 2026-11-18, which #674 adds; that pull request merges first, since these pages link its page. Refs: brig-sh/hull#105 Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
ananos
added a commit
that referenced
this pull request
Nov 19, 2026
The runtime now serves a divert, brig.internal and a published port on hull on Linux, so the pages that said it refuses them were wrong. They now put hull on Linux beside hvi: the same gateway, the same diverts and the same API for forwards. The measured run is the record of 2026-11-18, which #674 adds; that pull request merges first, since these pages link its page. Refs: brig-sh/hull#105 Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
ananos
added a commit
that referenced
this pull request
Nov 19, 2026
The runtime now serves a divert, brig.internal and a published port on hull on Linux, so the pages that said it refuses them were wrong. They now put hull on Linux beside hvi: the same gateway, the same diverts and the same API for forwards. The measured run is the record of 2026-11-18, which #674 adds; that pull request merges first, since these pages link its page. Refs: brig-sh/hull#105 Signed-off-by: Anastassios Nanos <ananos@nofire.ai>
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.
Summary
Brig puts a hull on Linux sandbox on a network gateway since #667, and refuses a policy, a divert and a published port there because no run on a real hull had shown they work. This is that run, on a fresh rootless install of brig-standalone-linux v0.1.0-rc22 (hull 4bf76a6, urunc 5c6bc70, hvi 0.1.0-rc.3, hull-assets 0.1.12) with Brig from main at cf80f90, on an amd64 host with KVM.
What holds: offline, isolated and shared postures; two isolated sandboxes cannot reach each other and a shared one cannot reach an isolated one; two shared ones can;
brig rm --all -yleaves no gateway. At hull level, with the flags and API calls Brig uses on macOS: an egress policy is enforced (allowed hosts 200, denied hosts refused at DNS and logged),brig.internaland a link-local divert are answered by the host sockets, and/forwardspublishes and withdraws a guest port.What does not: hull refuses an image whose
USERis a name, so the community images run only through their:roottags.The page also records the three things that cost time in this run so the next one avoids them. A separate change flips the capability rows this evidence supports.
Related issues
Refs brig-sh/hull#105.
Changes
docs/manual-tests/hull-linux-gateway-2026-11-18.md: the record.Checklist
make allpasses (vet, test, build)script/smoke.shpassesI have added or updated tests covering the changeI have rungo test ./... -race, if the change touches concurrency, subprocesses or the daemonI have exercised the change against a real runtime (brig run <agent>), if it touches the run, exec or credential path