Files
headscale/hscontrol
Kristoffer Dalby 22afb2c61b policy: fix asymmetric peer visibility with autogroup:self
When autogroup:self was combined with other ACL rules (e.g., group:admin
-> *:*), tagged nodes became invisible to users who should have access.

The BuildPeerMap function had two code paths:
- Global filter path: used symmetric OR logic (if either can access, both
  see each other)
- Autogroup:self path: used asymmetric logic (only add peer if that
  specific direction has access)

This caused problems with one-way rules like admin -> tagged-server. The
admin could access the server, but since the server couldn't access the
admin, neither was added to the other's peer list.

Fix by using symmetric visibility in the autogroup:self path, matching
the global filter path behavior: if either node can access the other,
both should see each other as peers.

Credit: vdovhanych <vdovhanych@users.noreply.github.com>

Fixes #2990
2026-01-21 14:35:16 +01:00
..
2025-12-18 10:02:23 +01:00
2025-09-09 09:40:00 +02:00
2026-01-20 17:13:38 +01:00
2026-01-16 14:54:04 +01:00
2025-12-17 12:32:04 +01:00
2025-09-09 09:40:00 +02:00
2025-12-10 15:55:15 +01:00
2025-12-10 15:55:15 +01:00
2025-12-10 15:55:15 +01:00
2025-12-10 15:55:15 +01:00