You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
tailscale/control/controlclient
Avery Pennarun 8a7d35594d ipnlocal: don't assume NeedsLogin immediately after StartLogout().
Previously, there was no server round trip required to log out, so when
you asked ipnlocal to Logout(), it could clear the netmap immediately
and switch to NeedsLogin state.

In v1.8, we added a true Logout operation. ipn.Logout() would trigger
an async cc.StartLogout() and *also* immediately switch to NeedsLogin.
Unfortunately, some frontends would see NeedsLogin and immediately
trigger a new StartInteractiveLogin() operation, before the
controlclient auth state machine actually acted on the Logout command,
thus accidentally invalidating the entire logout operation, retaining
the netmap, and violating the user's expectations.

Instead, add a new LogoutFinished signal from controlclient
(paralleling LoginFinished) and, upon starting a logout, don't update
the ipn state machine until it's received.

Updates: #1918 (BUG-2)
Signed-off-by: Avery Pennarun <apenwarr@tailscale.com>
4 years ago
..
auto.go ipnlocal: don't assume NeedsLogin immediately after StartLogout(). 4 years ago
client.go
controlclient_test.go ipnlocal: don't assume NeedsLogin immediately after StartLogout(). 4 years ago
debug.go
debug_test.go
direct.go
direct_test.go
hostinfo_linux.go
hostinfo_windows.go
map.go
map_test.go
sign.go
sign_supported.go
sign_unsupported.go
status.go ipnlocal: don't assume NeedsLogin immediately after StartLogout(). 4 years ago