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

[ISSUE WITH WSL NOT WINDOWS TERMINAL] Pasting from clipboard broken when running ssh-add.exe 2> /dev/null #19317

New Issue
Open
opened 2026-01-31 06:39:58 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 06:39:58 +00:00
Owner
Copy Link

Originally created by @OlJohnny on GitHub (Feb 5, 2023).

Windows Terminal version

1.15.3465.0

Windows build number

10.0.19045.0

Other Software

  • WSL2 with Ubuntu (C:\WINDOWS\system32\wsl.exe -d Ubuntu-20.04)
  • ssh-add.exe (OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2)

Steps to reproduce

  • You need to have a passphrase protected ssh key in your windows HOME/.ssh directory (just execute ssh-keygen in a PowerShell Terminal)
  • Start the Windows OpenSSH ssh-agent in an Administrator PowerShell Terminal Start-Service ssh-agent
  • Start WSL2 distribution in Windows Terminal
  • run ssh-add.exe and try to paste your passphrase

Expected Behavior

The passphrase gets pasted (without seeing it) and the key is successfully loaded into the ssh-agent.
This actually works, when running the WSL2 VM by just starting it from the Windows Search (i think it is then running inside cmd.exe) See comments below

Actual Behavior

The passphrase gets pasted so that you can see the text!
Also loading the key then fails, as ssh-add.exe seems to be unable to read the pasted passphrase.
NOTE: this may doesn't happen on the first try, but after running ssh-add -D and ssh-add again, it nearly always happens

Originally created by @OlJohnny on GitHub (Feb 5, 2023). ### Windows Terminal version 1.15.3465.0 ### Windows build number 10.0.19045.0 ### Other Software * WSL2 with Ubuntu (<code>C:\WINDOWS\system32\wsl.exe -d Ubuntu-20.04</code>) * ssh-add.exe (<code>OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2</code>) ### Steps to reproduce * You need to have a passphrase protected ssh key in your windows <code>HOME/.ssh</code> directory (just execute ssh-keygen in a PowerShell Terminal) * Start the Windows OpenSSH ssh-agent in an Administrator PowerShell Terminal <code>Start-Service ssh-agent</code> * Start WSL2 distribution in Windows Terminal * run <code>ssh-add.exe</code> and try to paste your passphrase ### Expected Behavior The passphrase gets pasted (without seeing it) and the key is successfully loaded into the <code>ssh-agent</code>. <s>This actually works, when running the WSL2 VM by just starting it from the Windows Search (i <i>think</i> it is then running inside cmd.exe)</s> See comments below ### Actual Behavior The passphrase gets pasted so that you can see the text! Also loading the key then fails, as ssh-add.exe seems to be unable to read the pasted passphrase. NOTE: this may doesn't happen on the first try, but after running <code>ssh-add -D</code> and <code>ssh-add</code> again, it nearly always happens
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 06:39:58 +00:00
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#19317
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?