Connor Peet

Some suggestions: - Use esbuild instead of webpack to build the bundles. Downside is this does involve a native bundler, which is hard to ship in a VS Code extension......

As far as I am aware, native-tls doesn't provide the primitives needed to implement SSH

I didn't know this was a thing, but can give it a poke...

Searching through the sources, I'm not sure what the `extensionHost` process is. I don't see a string with such casing in our source, and I don't reproduce this when running...

@SimonSiefke given you can still reproduce this, please run `ps -p -o args`, where `pid` is the PID in the right hand column of the `extensionHost` process. That should give...

ah, I was able to reproduce by using Remote SSH to connect to a Linux machine. But then debugging worked (well, I could connect, but as soon as the debugger...

Verification: there should no longer be a Debug option in the context menu if `--inspect(-port|-brk)=0` is present in the command line (since we don't know what port to connect to)

- Remote tunnels does not actively listen on any ports; it makes an outbound connection to an Azure service - Data over the tunnel is end-to-end encrypted, currently we use...

Circling back here, Dev Tunnels has added [group policies](https://learn.microsoft.com/en-us/azure/developer/dev-tunnels/policies) which VS Code respects as of 1.88, releasing next week.

Duplicates https://github.com/microsoft/vscode-js-debug/issues/1469. This is now released; run the `Check for Updates` command and restart VS Code to get the fix.