This commit is contained in:
Martin Aeschlimann 2021-12-14 19:11:57 +01:00
Родитель e6ba64211f
Коммит 768af2e166
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 2609A01E695523E3
1 изменённых файлов: 5 добавлений и 1 удалений

Просмотреть файл

@ -82,7 +82,7 @@ In the `settings.json`:
}
```
## WSL
## WSL (version 0.63.x)
The WSL - Remote extension now uses a new connection method for WSL 2 that tackles reconnection issues that can occur after hibernate and when working on machines with flaky internet connections. It should also help when working behind a proxy.
@ -91,3 +91,7 @@ Instead of using a socket connection to the WSL 2 VM address, it uses the `wsl.e
A new setting `remote.WSL2.connectionMethod` allows you to select the connection method. `wslExeProxy` is the new default. The other options are `wsl2VMAddress` (use a socket connection to the IP of the WSL2 VM) and `localhost` (use a socket connection to `localhost` and let Windows handle the proxy).
Please file issues against [vscode-remote-release](https://github.com/microsoft/vscode-remote-release/issues) if the new connection method does not work for you.
### Security update
Version 0.63.11 of the Remote-WSL extension includes a fix for a security issue in how the VS Code server running in the WSL distro is vulnerable to remote code execution. Details are in [CVE-2021-43907](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-43907).