mirror of
https://github.com/tailscale/tailscale.git
synced 2024-12-03 23:15:42 +00:00
37eab31f68
Instead of trying to use the user config dir, and then fail back to the OS temp dir, just always use the temp dir. Also use a filename that is less likely to cause collisions. This addresses an issue on a test synology instance that was mysteriously failing because there was a file at /tmp/tailscale. We could still technically run into this issue if a /tmp/tailscale-web-csrf.key file exists, but that seems far less likely. Updates tailscale/corp#13775 Signed-off-by: Will Norris <will@tailscale.com> |
||
|---|---|---|
| .. | ||
| build | ||
| src | ||
| dev.go | ||
| index.html | ||
| package.json | ||
| postcss.config.js | ||
| qnap.go | ||
| synology.go | ||
| tailwind.config.js | ||
| tsconfig.json | ||
| vite.config.ts | ||
| web_test.go | ||
| web.go | ||
| yarn.lock | ||