mirror of
https://github.com/juanfont/headscale.git
synced 2026-09-13 12:02:01 +09:00
2764e5f228
Regenerates ssh_results/*.hujson on top of the tscap fix (kradalby/tscap@833a50a + 837f1f6) that rewrites localpart:*@<domain> patterns in policy text alongside user email substitution. Before the fix, anonymized captures kept the raw @passkey domain in policy while the users landed on @example.com, so localpart:*@passkey matched zero users and headscale emitted only the wildcard rule, diffing against SaaS's per-user rules on 40 failing leaves across 14 scenarios (ssh-d2..d12 minus d1/d10, ssh-e6, ssh-f3..f5). With the new corpus: - localpart:*@passkey in policy → localpart:*@example.com - thor moves from thor@example.com to thor@dalby.cc so that "localpart:*@example.com" resolves to exactly odin+freya (matching SaaS output), and "localpart:*@dalby.cc" in ssh-d1 keeps matching exactly one user. Test code update: setupSSHDataCompatUsers() now pins thor on @dalby.cc to match the capture topologies. All other compat tests (routes, grants, acl, via-grant) use their own per-file topology loaders and are unaffected — thor's email change is scoped to the SSH hardcoded setup. TestSSHDataCompat: 41 failing leaves → 1 failing leaf. The single remaining ssh-b6/beedrill failure is a pre-existing, unrelated duplicate-principals bug in headscale's SSH compiler (same diff shape before and after this change). Updates #3157