Ability to store login details for SSH/telnet connections #13917

Closed
opened 2026-01-31 03:55:46 +00:00 by claunia · 2 comments
Owner

Originally created by @maninderdeol67 on GitHub (May 26, 2021).

Description of the new feature/enhancement

As much as I love the new Windows Terminal and all the fancy features that it offers, not being able to store the login details for my SSH or Telnet connections is kind of a deal-breaker for me.

As a Network guy, I roughly have 200+ devices that I connect to over SSH or Telnet, and some of them I access multiple times in a day so, having the ability to store the login details securely is crucial.

I have also tried setting up the SSH keys for authentication but, it becomes overwhelming very quickly as there are always new devices getting added. Sometimes, the device on the other end is not capable of storing SSH keys.

So, adding the ability to store username and password will make Windows Terminal a suitable replacement for something like M-Remote or Secure CRT.

Proposed technical implementation details (optional)

Originally created by @maninderdeol67 on GitHub (May 26, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement As much as I love the new Windows Terminal and all the fancy features that it offers, not being able to store the login details for my SSH or Telnet connections is kind of a deal-breaker for me. As a Network guy, I roughly have 200+ devices that I connect to over SSH or Telnet, and some of them I access multiple times in a day so, having the ability to store the login details securely is crucial. I have also tried setting up the SSH keys for authentication but, it becomes overwhelming very quickly as there are always new devices getting added. Sometimes, the device on the other end is not capable of storing SSH keys. So, adding the ability to store username and password will make Windows Terminal a suitable replacement for something like M-Remote or Secure CRT. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-FixArea-Extensibility labels 2026-01-31 03:55:46 +00:00
Author
Owner

@skyline75489 commented on GitHub (May 26, 2021):

As much I love the SSH features in SecureCRT, XShells, etc, I wouldn't really ask for similar features in Windows Terminal, since Terminal is not a professional SSH client.

See https://github.com/microsoft/terminal/issues/9486#issuecomment-798965251

@skyline75489 commented on GitHub (May 26, 2021): As much I love the SSH features in SecureCRT, XShells, etc, I wouldn't really ask for similar features in Windows Terminal, since Terminal is not a professional SSH client. See https://github.com/microsoft/terminal/issues/9486#issuecomment-798965251
Author
Owner

@zadjii-msft commented on GitHub (May 26, 2021):

Yea, the party line is that the Terminal is a great terminal emulator. That's what we're trying to be first and foremost - not a ssh client. This is a really good idea for someone to write an extension in the future (when those are supported, see #4000), but it's not something we'll be adding ourselves. Thanks!

@zadjii-msft commented on GitHub (May 26, 2021): Yea, the party line is that the Terminal is a great _terminal emulator_. That's what we're trying to be first and foremost - not a ssh client. This is a really good idea for someone to write an extension in the future (when those are supported, see #4000), but it's not something we'll be adding ourselves. Thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13917