Skip to content
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

clone ssh session support #5978

Closed
epiciskandar opened this issue May 19, 2020 · 5 comments
Closed

clone ssh session support #5978

epiciskandar opened this issue May 19, 2020 · 5 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@epiciskandar
Copy link

Description of the new feature/enhancement

first of all, I know Windows Terminal is not a pure SSH connection client, so is this really a reasonable good idea I'm not really sure.
please consider supporting "clone session", it's really useful for man who has to connect via “springboard machine / machine fortress” and through 2-factor(even 3-factor sometimes) verification/authentication.
application like SecureCRT has this function called "Clone Session". putty has similar "Duplication Session" but useless because that new connection is totally a raw flesh.

Proposed technical implementation details (optional)

@epiciskandar epiciskandar added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label May 19, 2020
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels May 19, 2020
@DHowett
Copy link
Member

DHowett commented May 19, 2020

Thank you for the request! It's possible to duplicate an open profile right now, but it's not possible for us to duplicate anything more than that. Here's why:

The important things about an SSH session are:

  • Username
  • Server
  • Password or Authentication Context

Since the username and the server can be encoded in the commandline, ctrl+shift+d can easily duplicate them. However, the password (or the authentication information) cannot be copied because Terminal is not going to get into the password business. It would increase the security risk of our project, and it's not a good feature for a generic terminal.

We have some requests for SSH session management, however. This might be a /dupe of #1280.

@ghost
Copy link

ghost commented May 19, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed May 19, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels May 19, 2020
@byteroll
Copy link

You could just add wsl.exe -- sshpass -p password ssh user@ip to Windows Terminal configurations.

@DHowett
Copy link
Member

DHowett commented Oct 14, 2021

Instead of storing your password in a Terminal profile, and in the commandline of an application (which is trivially accessible to any other application on the system), you should be using public key authentication.

@jaydu666
Copy link

jaydu666 commented Jun 7, 2022

I need "Duplication Session" too. using duplicate exist socket, not remember password.
like "openssh controlmaster", but windows not support unix socket.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

4 participants