-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenSSL: error:0A000152:SSL routines::unsafe legacy renegotiation disabled #8848
Comments
FYI I just fixed this by loading the workspace from VS Code instead of from WSL, updating all extensions—probably especially the WSL extension—and making sure everything was working from there. Then I shut down VS Code, and the next time I ran “code .” it worked! |
Yes. That was my workaround. |
I'm experiencing this same issue when running my dev container build, i assume it's why my extensions don't auto install.
When the install script runs I get this error
But nothing is shown in the exension host log
|
This has just started happening to me - only when I'm using Cisco VPN and under WSL2 (Ubuntu-22.04) |
This also started happening to me (behind a corporate firewall which does TLS decryption and re-encrypts it.)
|
This points to a configuration problem in the WSL distro: We use the installed |
@aeschli did you intend to close? |
Yes, my understanding is that this is a configuration issue on the OS side (WSL distro / docker container). As mentioned, what our script does is to call |
Ah so you added Is it also the case that your corporate MITM attack doesn't support secure renegotiation? That's what causes the error in my environment. Agree it's not a vscode issue but enabling unsafe renegotiation seems a bit reckless to me. |
Does this issue occur when all extensions are disabled?: Yes/No
Steps to Reproduce:
Result
Connecting to update.code.visualstudio.com (update.code.visualstudio.com)|13.107.213.31|:443... connected.
OpenSSL: error:0A000152:SSL routines::unsafe legacy renegotiation disabled
Unable to establish SSL connection.
I would have imagined this to be a common situation.
The text was updated successfully, but these errors were encountered: