mirror of
https://github.com/tailscale/tailscale.git
synced 2026-06-06 21:01:11 +08:00
f15a4f4416
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> |
||
|---|---|---|
| .. | ||
| build | ||
| src | ||
| assets.go | ||
| auth.go | ||
| index.html | ||
| package.json | ||
| qnap.go | ||
| styles.json | ||
| synology.go | ||
| tailwind.config.js | ||
| tsconfig.json | ||
| vite.config.ts | ||
| web_test.go | ||
| web.go | ||
| yarn.lock | ||