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

ssh features #11034

Closed
Mortaza-Seydi opened this issue Aug 25, 2021 · 3 comments
Closed

ssh features #11034

Mortaza-Seydi opened this issue Aug 25, 2021 · 3 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

@Mortaza-Seydi
Copy link

Mortaza-Seydi commented Aug 25, 2021

Description of the new feature/enhancement

i want to suggest some new features about ssh.

  1. password: store ssh passwords in ssh profiles and perform auto connect. so the user does not need to type passwords every time.
  2. sftp: users can see host files and abale to upload or download files.
  3. dynamic port forwarding: when user connect to ssh, he could add or remove any port forwards.
@Mortaza-Seydi Mortaza-Seydi added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Aug 25, 2021
@ghost ghost added 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 Aug 25, 2021
@Mortaza-Seydi Mortaza-Seydi changed the title store ssh password and auto connect ssh features Aug 25, 2021
@WSLUser
Copy link
Contributor

WSLUser commented Aug 25, 2021

Windows Terminal is not the place for storing passwords. Putty offers this as it's a dedicated to remote connections and includes a built-in password manager. However since VSCode allows this via extension such as https://github.com/SchoofsKelvin/vscode-sshfs or the official Remote-SSH, WT can support this via extension as well. Just needs to be tagged up in #4000

@zadjii-msft
Copy link
Member

Thanks for the feature request!

This would be a great opportunity for a plugin author once we get plugin support (#4000.)

I'm not sure that this sort of feature belongs in the terminal core -- we're focusing on making a great local terminal experience first and foremost -- and I think that anything we do internally would naturally play second fiddle to that. In light of that, I'm going to close this one out after linking it up to #4000 as an interesting thing that plugins could enable.

Thank you!

/dup #4653

@ghost
Copy link

ghost commented Aug 25, 2021

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 Aug 25, 2021
@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 Aug 25, 2021
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

3 participants