search

VSCodium / vscodium

binary releases of VS Code without MS branding/telemetry/licensing
https://vscodium.com
MIT License
25.29k stars 1.09k forks source link

`codium tunnel` doesn't work #1609

Closed nopeless closed 1 year ago

nopeless commented 1 year ago

Describe the bug codium tunnels seem to not work

Please confirm that this problem is VSCodium-specific

Please confirm that the issue/resolution isn't already documented

To Reproduce

codium tunnel

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Additional context

https://code.visualstudio.com/blogs/2022/07/07/vscode-server

https://code.visualstudio.com/docs/remote/tunnels

nopeless commented 1 year ago

reading a few other sources, I can see why it is disabled, but I believe it should at least give an explanation instead of giving the user code-tunnel-oss.exe ENOENT

myreprise1 commented 1 year ago

I really hope you all get this fixed since I haven't had much motivation to actually get anything done on my machine lately. It would be real nice if I could just open the tunnel on my iPad with vscode.dev and do everything on there.

StarLederer commented 1 year ago

As far as I understand command does not come with VSCode either, it is available separately in Code CLI which is downloaded also separately. I think VSCodium would have to build separate binaries for that if the CLI is open-source in the first place

nopeless commented 1 year ago

As far as I understand that command does not come with VSCode either, it is available separately in Code CLI which is downloaded separately. I think VSCodium would have to build separate binaries for that if the CLI is open-source in the first place

I might have overlooked my setup. I'll look into this again

daiyam commented 1 year ago

Fell free to do any PR. FYI, I haven't look at what tunnel even does. No time here.

nopeless commented 1 year ago

I just installed vscode solely for the tunnel and didn't think much of it. I feel like this should be closed for now.

JohnXLivingston commented 1 year ago

Fell free to do any PR. FYI, I haven't look at what tunnel even does. No time here.

Tunnel is a reverse shell. Enabling it creates huge security risk. Please never enable it (at least by default).

More info: https://ipfyx.fr/post/visual-studio-code-tunnel/

StarLederer commented 1 year ago

Well, so is the Remote - SSH, reverse-shell is kind of the goal... Of course this bares risks but I guess Microsoft is doing their best to inform people of that... maybe? I hope most people are running this in user-namespaced containers.

To be honest, I am not a fan of the tunnels at all anymore because I found out it completely relies on the Microsoft back-end but I guess this is how they fight open-source projects while still getting the benefits of maintaining one themselves.

  1. Create cool features that are hard to replicate.
  2. Promote the heck out of them.
  3. Someone tries Codium.
  4. One of the "cool features" doesn't work.
  5. "I wonder what else doesn't work in Codium. Maybe I should just stick with VS Code"
JohnXLivingston commented 1 year ago

Well, so is the Remote - SSH, reverse-shell is kind of the goal... Of course this bares risks but I guess Microsoft is doing their best to inform people of that... maybe? I hope most people are running this in user-namespaced containers.

I don't want to have to trust Microsoft. That's why i'm using codium, and not the original vscode. If this feature is enabled, I just hope I'll have a warning before (so i can find a way to secure my setup, wether by changing my IDE, or by configuring some things, like documented in the link i gave).

nopeless commented 1 year ago

Well, so is the Remote - SSH, reverse-shell is kind of the goal... Of course this bares risks but I guess Microsoft is doing their best to inform people of that... maybe? I hope most people are running this in user-namespaced containers.

To be honest, I am not a fan of the tunnels at all anymore because I found out it completely relies on the Microsoft back-end but I guess this is how they fight open-source projects while still getting the benefits of maintaining one themselves.

  1. Create cool features that are hard to replicate.
  2. Promote the heck out of them.
  3. Someone tries Codium.
  4. One of the "cool features" doesn't work.
  5. "I wonder what else doesn't work in Codium. Maybe I should just stick with VS Code"

may I ask what kind of tools you use as a substitute for tunnels? @StarLederer

daiyam commented 1 year ago

may I ask what kind of tools you use as a substitute for tunnels? @StarLederer

ngrok tcp 22

From a quick look, a VSCode tunnel seems to rely on a GitHub account to the share the ip. And since GitHub account aren't working on VSCodium. I don't think that feature will ever work.

StarLederer commented 1 year ago

@nopeless I use openvscode-server but I don't need all of what tunnels offer. Openvscode-server can probably be hosted over the web but I am using it to just open VS Code as a PWA in a container. Dev Containers are designed for my use-case but my container is built around Nix so I cannot run arbitrary binaries that that extension wants to run in the container. Instead I have to run VS Code "in the browser"

johndahl-now commented 1 year ago

Well, so is the Remote - SSH, reverse-shell is kind of the goal... Of course this bares risks but I guess Microsoft is doing their best to inform people of that... maybe? I hope most people are running this in user-namespaced containers.

It's not a SSH connection from user to user. The tunnel is established to Microsoft's servers permanently and allows access without SSH authentication. This is not simply a risk, this is a wide-open back door that allows Microsoft and hackers to have easy access to your system.

daiyam commented 1 year ago

allows access without SSH authentication.

Oh! That's bad.