jschoubben 0fcea460da route-proxy: serve an internal name to the private network only ...

The proxy answers public and internal names on the same listeners, so
serving an internal-only route made it reachable from the internet by
anyone sending its name. Requests and handshakes for an internal name
from outside the mesh range, loopback or a container bridge are now
answered as an unrouted name, and the 404 no longer lists them
(novox/hq issue 191, ADR 0138 insight of 2026-10-02).

2026-10-02 01:10:13 +02:00

..

authority_test.go

route-proxy: an ACME account belongs to the authority that issued it

2026-09-10 21:02:00 +02:00

challenge_test.go

route-proxy: a policy refusal is also not-my-token

2026-09-26 14:26:01 +02:00

Dockerfile

A route is a grant, and a provider is told where its consumer is

2026-08-31 02:43:19 +02:00

main.go

route-proxy: serve an internal name to the private network only

2026-10-02 01:10:13 +02:00

policy_test.go

route-proxy serves a route's internal-name alias, never certifies it

2026-09-25 17:24:13 +02:00

reach_test.go

route-proxy: serve an internal name to the private network only

2026-10-02 01:10:13 +02:00

routes_test.go

route-proxy: serve a route that names only its internal host

2026-10-01 23:31:57 +02:00