mlsmayconandClaude Fable 5.1 0df2eb7b25 [management] Refuse pins onto a host another account's gateway already claims ...

A host can be claimed by a pin as well as by a proxy row, and the proxy-row
check cannot see that. Another account's labeled pin beneath a host makes
the host its cluster, so a self-addressed endpoint on it would never be
served; another account's self-addressed endpoint on a host makes the proxy
declaring it theirs, so a label beneath it would never be served either.
Both bootstrap paths now refuse those shapes before the insert.

Neither question touches the shared-cluster shape: labeled pins under one
cluster are asked about in neither direction, so any number of accounts
still pin beneath a shared cluster. Two self-addressed endpoints on one
hostname stay the domain unique index's conflict to refuse.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Sa3DsBDP3VciAi4PPG17L6

2026-09-12 17:02:05 +00:00

..

controllers/network_map

[management] fix private services calc on new db path (#7383)

2026-09-01 20:20:30 +02:00

modules

[management] Refuse pins onto a host another account's gateway already claims

2026-09-12 17:02:05 +00:00

network_map_db

[management] update network_router_test to verify empty and nil peer_groups (#7425)

2026-09-04 15:29:51 +02:00

server

[management] Expire unvalidated custom domain registrations (#7497)

2026-09-11 17:57:58 +02:00

shared

[management] extract peer update logic and wrap it in tests (#7338)

2026-09-11 17:07:26 +02:00