Skip to content

Feature idea - open ssh via external tool #89

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

Open
flosch-dev opened this issue Mar 26, 2025 · 6 comments
Open

Feature idea - open ssh via external tool #89

flosch-dev opened this issue Mar 26, 2025 · 6 comments

Comments

@flosch-dev
Copy link

not sure if this is feasible, but maybe it would be nice to open ssh sessions via external tool like windows terminal instead of VScode build in terminal.

@kaelemc
Copy link
Member

kaelemc commented Mar 27, 2025

Can use ssh protocol handler for this. I know that SecureCRT and PuTTY can register to it. Off the top of my head not sure how that'd work with Windows terminal.

@FloSch62
Copy link
Member

It all depends a bit which tool is used. Some tools do not offer args to initiate a ssh connection. For example for MobaXterm I have not found a possibility. What I can think about, also with a look on other OSes as windows, it to make it freely configurable with vars like:

ExternalSSH: "C:\putty.exe -ssh ${user}@${host}"

Means a user need to provide the path to its external ssh tool a create the args, while the extension provides the container ip and the user...

@flosch-dev
Copy link
Author

running native ssh client with regular openssh args should be fine. In windows you can change default terminal program so that windows terminal is used.
Config vars might be even more flexible, but native openssh should be available on all OS today

@kaelemc
Copy link
Member

kaelemc commented Mar 28, 2025

It all depends a bit which tool is used. Some tools do not offer args to initiate a ssh connection. For example for MobaXterm I have not found a possibility. What I can think about, also with a look on other OSes as windows, it to make it freely configurable with vars like:

ExternalSSH: "C:\putty.exe -ssh ${user}@${host}"

Means a user need to provide the path to its external ssh tool a create the args, while the extension provides the container ip and the user...

I think I agree with this method. It's much more flexible and good for other OSes.

@asadarafat
Copy link
Contributor

@kaelemc
Copy link
Member

kaelemc commented May 2, 2025

I have some rough implementation currently, the placeholders are working fine for user, hostname etc.

The issue is that most users are using Remote SSH, so we need to do some port forwarding or SSH tunneling for this to be useful.

Also when using Remote-SSH, we are forced to use the protocol handler as we can't execute commands on the clientside.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants