You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support local privileged ports for port forwarding with SSH and Containers #4589
Remote extensions that provide their own port forwarding mechanism can already support this.
SSH and Containers use the built in forwarding mechanism, and would benefit from allowing privileged local ports too.
Reacted by Alex, Marc-Antoine Couture, Ali Yousuf, Johan Brandhorst-Satzkorn, Shahin Agha-Ghassem, Toma Becea, Lázaro Fernández, Jose Manuel Benavides, ᒍ ᗩ ᑕ K , Nishikawa Daisaku and 37 more
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 10 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
This feature request has not yet received the 10 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
🙁 In the last 60 days, this feature request has received less than 10 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
This would be an excellent feature to have, and remove the confusing socat workaround for the moment. There doesn't seem to be a consistent way to forward a privileged port to a specific non-privileged port, so the port forwarding needs to be manually set up by a user in the current state.
Reacted by Anton Kosyakov, Ivan Rizzante and thang1160
My lazy solution is to lower unprivileged ports down to 80. Is it safe? No, but it works without any extra steps later on.
Edit /etc/sysctl.conf and add a new line net.ipv4.ip_unprivileged_port_start = 80
Activity
vscode-triage-bot commentedon Mar 3, 2021
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 10 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
vscode-triage-bot commentedon Apr 23, 2021
This feature request has not yet received the 10 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding
vscode-triage-bot commentedon May 4, 2021
🙁 In the last 60 days, this feature request has received less than 10 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
jonathanlaf commentedon Mar 24, 2022
Any ETA ?
marcantoinecouture commentedon Jun 15, 2022
Any ETA?
ozette-manzt commentedon Sep 28, 2022
This would be an excellent feature to have, and remove the confusing
socatworkaround for the moment. There doesn't seem to be a consistent way to forward a privileged port to a specific non-privileged port, so the port forwarding needs to be manually set up by a user in the current state.thang1160 commentedon Jan 25, 2023
My lazy solution is to lower unprivileged ports down to 80. Is it safe? No, but it works without any extra steps later on.
Edit
/etc/sysctl.confand add a new linenet.ipv4.ip_unprivileged_port_start = 80