tailscale/client
Andrew Lytvynov f15a4f4416
client/web: move API permission checks into handlers (#19576)
There are only a couple endpoints that check peer capabilities. Keeping
permission checks with the code that assumes they were performed, rather
than with the routing layer, feels easier to reason about.

Check that the caller is actually a peer and pass their capabilities via
a context value for handlers that want to check them.

Along with this, simplify the helper handler wrappers that are not
needed for most of the endpoints.

Updates #40851

Signed-off-by: Andrew Lytvynov <awly@tailscale.com>
2026-05-01 09:01:53 -07:00
..
freedesktop cmd/vet: add subtestnames analyzer; fix all existing violations 2026-04-05 15:52:51 -07:00
local client/local, ipn/localapi, ipn/ipnlocal: add PeerByID 2026-05-01 06:20:46 -07:00
systray client/systray: support several different color themes 2026-04-27 18:54:14 -07:00
tailscale cmd/vet: add subtestnames analyzer; fix all existing violations 2026-04-05 15:52:51 -07:00
web client/web: move API permission checks into handlers (#19576) 2026-05-01 09:01:53 -07:00