starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 07:54:35 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

sendInput not working with ssh #21998

New Issue
Closed
opened 2026-01-31 08:00:25 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:00:25 +00:00
Owner
Copy Link

Originally created by @CodeDok on GitHub (Jul 23, 2024).

Windows Terminal version

1.20.11781.0 and 1.21.240626002-preview

Windows build number

10.0.19045

Other Software

OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2

Steps to reproduce

Install SSH Server (optional)

For Testing: WSL2 with OpenSSH

sudo apt install openssh-server
sudo systemctl enable ssh
sudo systemctl start ssh
ip address show

JSON (Fragment)

Profile

{
    "name": "wsl",
    "commandline": "ssh <user>@<ip of wsl>"
}

Action (in Fragment if preview version)

        {
            "command": {
                "action": "multipleActions",
                "actions": 
                [
                    {
                        "action": "newTab",
                        "profile": "wsl",
                        "tabTitle": "Test"
                    },
                    {
                        "action": "sendInput",
                        "input": "<password>"
                    }
                ]
            },
            "name": "wsl"
        },

Unfortunately I don't know how to send an ENTER but when I manually press ENTER there is no input from sendInput because nothing was inserted into the password field.

It's just an example for those questioning the sendInput with a password. If I want to send other inputs like sourcing an custom bashrc into an ssh session established via keys it also does not work.

Would be a nice addition to know whether its possible to press ENTER in an sendInput. I have not really found a source for reliable keypresses. I tried a few ASCII Escape Sequences from https://gist.github.com/fnky/458719343aabd01cfb17a3a4f7296797, but not much luck except for the arrow keys.

Thank you very much!

Expected Behavior

It inserts the sendInput value into the terminal like it's typed by an keyboard.

Actual Behavior

Does nothing

Originally created by @CodeDok on GitHub (Jul 23, 2024). ### Windows Terminal version 1.20.11781.0 and 1.21.240626002-preview ### Windows build number 10.0.19045 ### Other Software OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2 ### Steps to reproduce # Install SSH Server (optional) ## For Testing: WSL2 with OpenSSH ```batchfile sudo apt install openssh-server sudo systemctl enable ssh sudo systemctl start ssh ip address show ``` # JSON (Fragment) ## Profile ```json { "name": "wsl", "commandline": "ssh <user>@<ip of wsl>" } ``` ## Action (in Fragment if preview version) ```json { "command": { "action": "multipleActions", "actions": [ { "action": "newTab", "profile": "wsl", "tabTitle": "Test" }, { "action": "sendInput", "input": "<password>" } ] }, "name": "wsl" }, ``` Unfortunately I don't know how to send an `ENTER` but when I manually press `ENTER` there is no input from sendInput because nothing was inserted into the password field. It's just an example for those questioning the sendInput with a password. If I want to send other inputs like sourcing an custom bashrc into an ssh session established via keys it also does not work. Would be a nice addition to know whether its possible to press `ENTER` in an sendInput. I have not really found a source for reliable keypresses. I tried a few ASCII Escape Sequences from https://gist.github.com/fnky/458719343aabd01cfb17a3a4f7296797, but not much luck except for the arrow keys. Thank you very much! ### Expected Behavior It inserts the sendInput value into the terminal like it's typed by an keyboard. ### Actual Behavior Does nothing
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:00:25 +00:00
claunia commented 2026-01-31 08:00:26 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jul 23, 2024):

Actions are executed one after another without waiting on anything. Without having debugged this, I suspect what happens is that by the time the sendInput action runs, newTab hasn't actually finished setting up the tab yet. As such the input gets lost. We could consider fixing this, because it's probably possible to set up the connection synchronously.

To answer your other question: The "enter key" is actually the key on your numblock (bottom right). The correct name for the one in the middle of the keyboard is technically the "return key". As the name indicates, the character that the return key sends is the carriage return \r. The solution is to use "input": "<password>\r".

But please do not put your SSH password in your settings file and especially not in a sendInput action. That's simply not safe. ~/.ssh is certainly already guarded by pretty much every AV scanner on the market, whereas our settings directory most likely isn't. Instead, use SSH keys if you can (preferably Ed25519). If you need help setting up a ssh key pair, please let me know. (You should find plenty instructions on the internet already though.)

@lhecker commented on GitHub (Jul 23, 2024): Actions are executed one after another without waiting on anything. Without having debugged this, I suspect what happens is that by the time the sendInput action runs, newTab hasn't actually finished setting up the tab yet. As such the input gets lost. We could consider fixing this, because it's probably possible to set up the connection synchronously. To answer your other question: The "enter key" is actually the key on your numblock (bottom right). The correct name for the one in the middle of the keyboard is technically the "return key". As the name indicates, the character that the return key sends is the carriage return `\r`. The solution is to use `"input": "<password>\r"`. But *please* do not put your SSH password in your settings file and especially not in a sendInput action. That's simply not safe. `~/.ssh` is certainly already guarded by pretty much every AV scanner on the market, whereas our settings directory most likely isn't. Instead, use SSH keys if you can (preferably Ed25519). If you need help setting up a ssh key pair, please let me know. (You should find plenty instructions on the internet already though.)
claunia commented 2026-01-31 08:00:27 +00:00
Author
Owner
Copy Link

@CodeDok commented on GitHub (Jul 23, 2024):

Thank you for the enter key!

That would make sense if the actions are not dependent on the outcome of the previous action. Do you know whether it is even possible to check the completion state or result of an executed action?

Definitely do not persist any password as clear text in any config files! I just used it as a relatively easy example to reproduce the behaviour. :)

Not quite sure how we should proceed. Should I create a feature request or should we keep it as bug?

@CodeDok commented on GitHub (Jul 23, 2024): Thank you for the enter key! That would make sense if the actions are not dependent on the outcome of the previous action. Do you know whether it is even possible to check the completion state or result of an executed action? Definitely do not persist any password as clear text in any config files! I just used it as a relatively easy example to reproduce the behaviour. :) Not quite sure how we should proceed. Should I create a feature request or should we keep it as bug?
claunia commented 2026-01-31 08:00:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 23, 2024):

We don't need to keep this open, we've already got: /dip #13444

Thanks!

@zadjii-msft commented on GitHub (Jul 23, 2024): We don't need to keep this open, we've already got: /dip #13444 Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21998
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?