coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Orientation §2: bao.coulomb.social now serves a trusted notice page (RPF-WP-0047)
Some checks are pending
CI Smoke / host-smoke (push) Waiting to run
Details
CI Smoke / container-smoke (push) Waiting to run
Details

Browse source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
codex 2026-09-24 02:22:02 +02:00
parent 1e37bcda18
commit 2120e7d887
2 changed files with 6 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/inner-zone-access-without-a-company-network.md
View file

@ -59,6 +59,7 @@ is the default posture and there is no considered answer for BYOD access.
The retraction stands. The OpenBao UI is unchanged and reachable through the
`openbao-ui-railiance01` tunnel at `http://127.0.0.1:18200/ui/`; nothing was made
headless. Separately, `bao.coulomb.social` is to stop serving a broken-looking
TLS error and serve a plain "not publicly available" page instead — requested of
railiance-platform on 2026-09-23, tracked there, and not part of this question.
headless. Separately, `bao.coulomb.social` now serves a plain "not publicly available"
page on a trusted certificate instead of a self-signed TLS error (railiance-platform
RPF-WP-0047, live 2026-09-23, verified from outside 2026-09-24). That closed the
broken-looking surface; it did not answer this question.