mirror of
https://github.com/tailscale/tailscale.git
synced 2024-11-26 03:25:35 +00:00
90fd04cbde
I realized that a lot of the problems that we're seeing around migration and LocalBackend state can be avoided if we drive Windows pref migration entirely from within tailscaled. By doing it this way, tailscaled can automatically perform the migration as soon as the connection with the client frontend is established. Since tailscaled is already running as LocalSystem, it already has access to the user's local AppData directory. The profile manager already knows which user is connected, so we simply need to resolve the user's prefs file and read it from there. Of course, to properly migrate this information we need to also check system policies. I moved a bunch of policy resolution code out of the GUI and into a new package in util/winutil/policy. Updates #7626 Signed-off-by: Aaron Klotz <aaron@tailscale.com> |
||
|---|---|---|
| .. | ||
| childproc | ||
| debug.go | ||
| depaware.txt | ||
| generate.go | ||
| install_darwin.go | ||
| install_windows.go | ||
| manifest_windows_386.syso | ||
| manifest_windows_amd64.syso | ||
| manifest_windows_arm64.syso | ||
| proxy.go | ||
| required_version.go | ||
| ssh.go | ||
| taildrop.go | ||
| tailscaled_bird.go | ||
| tailscaled_notwindows.go | ||
| tailscaled_test.go | ||
| tailscaled_windows.go | ||
| tailscaled.defaults | ||
| tailscaled.go | ||
| tailscaled.openrc | ||
| tailscaled.service | ||
| windows-manifest.xml | ||
| with_cli.go | ||