-
Notifications
You must be signed in to change notification settings - Fork 309
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
code-server launcher should forward --socket-path to the underlying server #6940
Comments
Thanks for the issue. Currently, we listen on a port since the underlying infrastructure and client we use from another team is designed as a port forwarding service. However, we hope to soon build native integration to their service in our CLI and their SDK, which would let us avoid having to listen anywhere, since we can connect incoming connections directly to the control server. This will also let us avoid having to download the port forwarding utility, and let us implement port forwarding. |
I think @leifwalsh talks about |
Ah, right, missed that... |
Yeah, for serve-local, thanks @aeschli |
What are some verif steps for this? |
|
actually, I didn't work on this, so I did that and just verified it 😛 |
There are two things called
code-server
, I'm not sure how you refer to them internally, but I'll call https://aka.ms/vscode-server-launcher/x86_64-unknown-linux-gnu the launcher and https://update.code.visualstudio.com/commit:b06ae3b2d2dbfe28bca3134cc6be65935cdfea6a/server-linux-x64-web/stable, which that downloads, the server.The server supports
--socket-path
, which makes it listen on a unix domain socket, which is great for security. We can use that, and send it traffic through a reverse proxy that terminates authentication in the way we like to do authentication internally. Having the server listen on a localhost TCP port is less secure on shared hosts.But, the launcher only supports
--host
and--port
, it doesn't know about--socket-path
. Could we make the launcher forward the--socket-path
argument along forcode-server serve-local --socket-path
?The text was updated successfully, but these errors were encountered: