diff options
| author | Mario Minardi <mario@tailscale.com> | 2024-11-26 10:45:03 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-11-26 10:45:03 -0700 |
| commit | 26de518413277e0869b815c373f694f6b5d18562 (patch) | |
| tree | b71e8506b287d754d6e92cb3a7a3aa28ba1f0103 /control/controlhttp/controlhttpserver/controlhttpserver.go | |
| parent | 4d33f30f91eb7debdf90c8770990801f3857e30c (diff) | |
| download | tailscale-26de518413277e0869b815c373f694f6b5d18562.tar.xz tailscale-26de518413277e0869b815c373f694f6b5d18562.zip | |
ipn/ipnlocal: only check CanUseExitNode if we are attempting to use one (#14230)
In https://github.com/tailscale/tailscale/pull/13726 we added logic to
`checkExitNodePrefsLocked` to error out on platforms where using an
exit node is unsupported in order to give users more obvious feedback
than having this silently fail downstream.
The above change neglected to properly check whether the device in
question was actually trying to use an exit node when doing the check
and was incorrectly returning an error on any calls to
`checkExitNodePrefsLocked` on platforms where using an exit node is not
supported as a result.
This change remedies this by adding a check to see whether the device is
attempting to use an exit node before doing the `CanUseExitNode` check.
Updates https://github.com/tailscale/corp/issues/24835
Signed-off-by: Mario Minardi <mario@tailscale.com>
Diffstat (limited to 'control/controlhttp/controlhttpserver/controlhttpserver.go')
0 files changed, 0 insertions, 0 deletions