starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

ctrl+u in password contexts does not produce the expected results with WSL #6151

New Issue
Closed
opened 2026-01-31 00:31:05 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 00:31:05 +00:00
Owner
Copy Link

Originally created by @richardnpaul on GitHub (Jan 26, 2020).

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]

Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Windows Terminal version (if applicable):

Version: 0.8.10091.0

Steps to reproduce

  1. Create an SSH key with passphrase set and use this SSH key to ssh to a remote machine, in WSL. When prompted for the passphrase, mistype something, press Ctrl+u key combination and type the correct password.
  2. Alternatively, in WSL, attempt to su to an account which has a password, or perform a command with sudo and when prompted for the password, mistype, press ctrl+u and type the correct password.

Expected behavior

  1. The SSH key should be decrypted correctly and you should be connected via SSH to the remote machine.
  2. The password should be accepted and the account switched or the sudo command performed.

Actual behavior

  1. Reprompted for the password. Type it in correctly and this just works.
  2. Reprompted for the password. Type it in correctly and this just works.

I don't actually know or understand what's going on in the background here but this is a fairly frequently used shortcut with reasonably long&/complex passwords.

I added { "command": null, "keys": ["ctrl+u"] }, to my profile.json without improvement.

Originally created by @richardnpaul on GitHub (Jan 26, 2020). # Environment ``` Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] ``` > Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 ``` Windows Terminal version (if applicable): ``` > Version: 0.8.10091.0 # Steps to reproduce 1. Create an SSH key with passphrase set and use this SSH key to ssh to a remote machine, in WSL. When prompted for the passphrase, mistype something, press `Ctrl+u` key combination and type the correct password. 2. Alternatively, in WSL, attempt to `su` to an account which has a password, or perform a command with `sudo` and when prompted for the password, mistype, press `ctrl+u` and type the correct password. # Expected behavior 1. The SSH key should be decrypted correctly and you should be connected via SSH to the remote machine. 2. The password should be accepted and the account switched or the sudo command performed. # Actual behavior 1. Reprompted for the password. Type it in correctly and this just works. 2. Reprompted for the password. Type it in correctly and this just works. --- I don't actually know or understand what's going on in the background here but this is a fairly frequently used shortcut with reasonably long&/complex passwords. I added `{ "command": null, "keys": ["ctrl+u"] },` to my profile.json without improvement.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 00:31:06 +00:00
claunia commented 2026-01-31 00:31:06 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 26, 2020):

Sorry, what is ctrl+u supposed to do when it’s working?

@DHowett-MSFT commented on GitHub (Jan 26, 2020): Sorry, what is ctrl+u supposed to do when it’s working?
claunia commented 2026-01-31 00:31:07 +00:00
Author
Owner
Copy Link

@richardnpaul commented on GitHub (Jan 26, 2020):

Sorry, what is ctrl+u supposed to do when it’s working?

Terribly sorry, it's supposed to clear to the left of the cursor. You can this this working in WSL by typing something into the terminal and then using the ctrl+u combo. ctrl+k instead of ctrl+u clears to the right.

@richardnpaul commented on GitHub (Jan 26, 2020): > Sorry, what is ctrl+u supposed to do when it’s working? Terribly sorry, it's supposed to clear to the left of the cursor. You can this this working in WSL by typing something into the terminal and then using the `ctrl+u` combo. `ctrl+k` instead of `ctrl+u` clears to the right.
claunia commented 2026-01-31 00:31:07 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 26, 2020):

Wow, this is actually kinda crazy. It looks like ^U is handled by the tty itself. A compliant terminal emulator must send U+0015 NAK (␕), and it's up to the thing on the other end to handle it properly.

Unfortunately, that makes this a WSL issue (and not something Terminal can really help with) -- its tty implementation isn't handling NAK as kill-line.

Sorry!

@DHowett-MSFT commented on GitHub (Jan 26, 2020): Wow, this is actually kinda crazy. It looks like `^U` is handled _by the tty itself_. A compliant terminal emulator must send `U+0015 NAK` (␕), and it's up to the thing on the other end to handle it properly. Unfortunately, that makes this a WSL issue (and not something Terminal can really help with) -- its tty implementation isn't handling NAK as kill-line. Sorry!
claunia commented 2026-01-31 00:31:07 +00:00
Author
Owner
Copy Link

@richardnpaul commented on GitHub (Jan 26, 2020):

Wow, this is actually kinda crazy. It looks like ^U is handled by the tty itself. A compliant terminal emulator must send U+0015 NAK (␕), and it's up to the thing on the other end to handle it properly.

Unfortunately, that makes this a WSL issue (and not something Terminal can really help with) -- its tty implementation isn't handling NAK as kill-line.

Sorry!

I suspected as much. Thanks for checking this though. Is there some way to get this resolved in WSL do you know? Nevermind, I found the WSL repo for reporting issues

@richardnpaul commented on GitHub (Jan 26, 2020): > > > Wow, this is actually kinda crazy. It looks like `^U` is handled _by the tty itself_. A compliant terminal emulator must send `U+0015 NAK` (␕), and it's up to the thing on the other end to handle it properly. > > Unfortunately, that makes this a WSL issue (and not something Terminal can really help with) -- its tty implementation isn't handling NAK as kill-line. > > Sorry! I suspected as much. Thanks for checking this though. ~Is there some way to get this resolved in WSL do you know?~ Nevermind, I found the WSL repo for reporting issues
claunia commented 2026-01-31 00:31:07 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 26, 2020):

(I bet this will work in WSL2, since it actually uses the Linux kernel (and therefore a good tty driver!))

@DHowett-MSFT commented on GitHub (Jan 26, 2020): (I bet this will work in WSL2, since it actually uses the Linux kernel (and therefore a good tty driver!))
claunia commented 2026-01-31 00:31:07 +00:00
Author
Owner
Copy Link

@richardnpaul commented on GitHub (Jan 26, 2020):

(I bet this will work in WSL2, since it actually uses the Linux kernel (and therefore a good tty driver!))

Spot on it does indeed work correctly in WSL2

@richardnpaul commented on GitHub (Jan 26, 2020): > (I bet this will work in WSL2, since it actually uses the Linux kernel (and therefore a good tty driver!)) Spot on it does indeed work correctly in WSL2
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 Needs-Tag-Fix 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#6151
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?