Groundwork for the app gate (item 1): before anything can enforce authentication on app ports, the node has to know which ports are *supposed* to be reachable without it. `PortMapping` grows `auth` (PortAuth::Session | None, defaulting to Session) and `auth_rationale`. The default is deliberately the protected one. Every app port on this node answered with no credential at all over LAN, Tailscale, Tor and the FIPS mesh alike — reproduced 2026-08-03 — precisely because exposure was what you got by saying nothing. Inverting the default means a new app is protected unless its manifest argues for an exemption. Validation makes the argument mandatory: `auth: none` without a rationale is rejected, and so is a rationale without `auth: none` (that combination means the author wrote an exemption and did not get one — shipping it silently would leave them believing otherwise). 17 ports across 12 apps are declared exempt, each with its reason. They are the ports that cannot sit behind an HTTP login page at all: Lightning p2p (BOLT-8 noise), LND gRPC/REST and CLN gRPC (macaroon / mutual TLS — Zeus and remote wallets dial these directly), Bitcoin p2p gossip, electrum wire protocol, Wyoming voice streams, git-over-SSH, and the UDP discovery protocols (mDNS, SSDP, STUN). Everything else — 39 published ports — now defaults to gated. Bitcoin's RPC 8332 is deliberately NOT exempted: it is already `bind: 127.0.0.1`, so the gate never sees it, and claiming an exemption it does not need would put a line in the audit list that means nothing. If the loopback bind is ever dropped, it fails closed. Two corpus tests keep this honest: every shipped manifest must parse under the new rules, and the exempt set is pinned at 17 so any change to the node's unauthenticated surface has to be a deliberate edit. Tests: 73/73 archipelago-container, workspace builds clean. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
70 lines
1.7 KiB
YAML
70 lines
1.7 KiB
YAML
app:
|
|
id: core-lightning
|
|
name: Core Lightning (CLN)
|
|
version: 23.08.2
|
|
description: Lightning Network implementation in C. Lightweight alternative to LND.
|
|
|
|
container:
|
|
image: elementsproject/lightningd:v23.08.2
|
|
image_signature: cosign://...
|
|
pull_policy: verify-signature
|
|
|
|
dependencies:
|
|
- app_id: bitcoin-core
|
|
version: ">=26.0"
|
|
|
|
resources:
|
|
cpu_limit: 1
|
|
memory_limit: 512Mi
|
|
disk_limit: 5Gi
|
|
|
|
security:
|
|
capabilities: [NET_BIND_SERVICE]
|
|
readonly_root: true
|
|
no_new_privileges: true
|
|
user: 1000
|
|
seccomp_profile: default
|
|
network_policy: isolated
|
|
apparmor_profile: core-lightning
|
|
|
|
ports:
|
|
- host: 9736
|
|
container: 9735
|
|
protocol: tcp # P2P (using 9736 to avoid conflict with LND)
|
|
auth: none
|
|
auth_rationale: >-
|
|
Lightning p2p. The BOLT-8 noise handshake authenticates and encrypts the channel itself.
|
|
- host: 9835
|
|
container: 9835
|
|
protocol: tcp # gRPC
|
|
auth: none
|
|
auth_rationale: >-
|
|
Core Lightning gRPC, authenticated by mutual TLS client certificates.
|
|
|
|
volumes:
|
|
- type: bind
|
|
source: /var/lib/archipelago/core-lightning
|
|
target: /home/clightning/.lightning
|
|
options: [rw]
|
|
|
|
environment:
|
|
- BITCOIND_RPCURL=http://bitcoin-core:8332
|
|
- BITCOIND_RPCUSER=${BITCOIN_RPC_USER}
|
|
- BITCOIND_RPCPASS=${BITCOIN_RPC_PASSWORD}
|
|
- NETWORK=bitcoin
|
|
|
|
health_check:
|
|
type: exec
|
|
endpoint: lightning-cli getinfo
|
|
interval: 30s
|
|
timeout: 5s
|
|
retries: 3
|
|
|
|
bitcoin_integration:
|
|
rpc_access: admin
|
|
sync_required: true
|
|
|
|
lightning_integration:
|
|
channel_management: true
|
|
payment_routing: true
|