Esta es una versión anterior. La versión actual es 1.104.2. Tailscale 1.104.2 · Fecha de publicación:
Archivos de instalación 1.98.9
| Arquitectura | Tipo | Ámbito | Tamaño del archivo | Descargar | SHA256 |
|---|---|---|---|---|---|
| 64 bits | EXE (WiX Burn) | Todos los usuarios | 107,8 MB | pkgs.tailscale.com | VirusTotal |
| 64 bits | MSI | Todos los usuarios | 36,5 MB | pkgs.tailscale.com | VirusTotal |
| ARM64 | EXE (WiX Burn) | Todos los usuarios | 107,8 MB | pkgs.tailscale.com | VirusTotal |
| ARM64 | MSI | Todos los usuarios | 34,2 MB | pkgs.tailscale.com | VirusTotal |
| 32 bits | EXE (WiX Burn) | Todos los usuarios | 107,8 MB | pkgs.tailscale.com | VirusTotal |
| 32 bits | MSI | Todos los usuarios | 35,7 MB | pkgs.tailscale.com | VirusTotal |
El enlace y el SHA256 proceden del manifiesto comunitario del Administrador de paquetes de Windows. Conviene comparar el hash del archivo descargado antes de ejecutarlo.
Notas de la versión
All Platforms
- Fixed: Tailscale SSH Unix socket forwarding respects symlink permissions. This fix addresses a security vulnerability described in TS-2026-004.
- Fixed: Tailscale Serve Unix socket proxy targets are restricted to the root user. This fix addresses a security vulnerability described in TS-2026-005.
- Fixed: Tailscale SSH does not allow the use of UIDs or numeric-only usernames. This fix addresses a security vulnerability described in TS-2026-006.
- Fixed: Nodes advertising Tailscale Services filter and reject packets from service IPs on ports they do not advertise. This fix addresses a security vulnerability described in TS-2026-007.
- Fixed: Tailscale Serve and Tailscale Funnel terminate path walks for non-absolute paths, preventing CPU core pinning. This fix addresses a security vulnerability described in TS-2026-008.
- Fixed: Tailscale SSH does not allow the use of usernames with leading dashes. This fix addresses a security vulnerability described in TS-2026-009.
- Fixed: An issue where a user could be logged out of Tailscale when changing the tag on a device via CLI has been resolved.
