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

Unexpexted behavior with whitespace characters in interactive mode #23540

New Issue
Open
opened 2026-01-31 08:45:18 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 08:45:18 +00:00
Owner
Copy Link

Originally created by @a-528 on GitHub (Aug 24, 2025).

Windows Terminal version

1.22.12111.0

Windows build number

10.0.19045.6216

Other Software

Command Prompt
Powershell
Bash

Steps to reproduce

This bug was discovered while using Kopia and age (encryption tool).

Kopia example:
I tried connecting to a repository with kopia repository connect filesystem --path /path/to/repo, but got an error after entering my password. The error presents in interactive mode.

Using Command Prompt, Powershell and bash with WSL2 through Windows Terminal all failed when entering my password. If I used Command Prompt, Powershell or bash standalone, no error happened and I could connect.

age example:
A file encrypted with age through Windows Terminal, no matter the shell, can only be decrypted with Windows Terminal. Using the standalone shells gives incorrect password error.

Likewise encrypting a file through a standalone shell, will result in error if Windows Terminal is used to attempt decryption.

The problem:
My testing has shown that Windows Terminal isn't correctly handling the passwords in interactive mode if they have trailing whitespace characters. Example of such password entered in interactive mode is "passwd123 ".

I imagine there's quite a few other cases where this different behavior could impact end users.

Expected Behavior

As a normal end user I except Windows Terminal to pass my complete input.

Actual Behavior

Widows Terminal removes trailing whitespace characters from input (demonstrated in interactive mode). I do not know if this bug could impact usage outside of interactive move.

Originally created by @a-528 on GitHub (Aug 24, 2025). ### Windows Terminal version 1.22.12111.0 ### Windows build number 10.0.19045.6216 ### Other Software Command Prompt Powershell Bash ### Steps to reproduce This bug was discovered while using Kopia and age (encryption tool). **Kopia example:** I tried connecting to a repository with `kopia repository connect filesystem --path /path/to/repo`, but got an error after entering my password. The error presents in interactive mode. Using Command Prompt, Powershell and bash with WSL2 through Windows Terminal all failed when entering my password. If I used Command Prompt, Powershell or bash standalone, no error happened and I could connect. **age example:** A file encrypted with age through Windows Terminal, no matter the shell, can only be decrypted with Windows Terminal. Using the standalone shells gives incorrect password error. Likewise encrypting a file through a standalone shell, will result in error if Windows Terminal is used to attempt decryption. **The problem:** My testing has shown that Windows Terminal isn't correctly handling the passwords in interactive mode if they have trailing whitespace characters. Example of such password entered in interactive mode is "passwd123 ". I imagine there's quite a few other cases where this different behavior could impact end users. ### Expected Behavior As a normal end user I except Windows Terminal to pass my complete input. ### Actual Behavior Widows Terminal removes trailing whitespace characters from input (demonstrated in interactive mode). I do not know if this bug could impact usage outside of interactive move.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:45:18 +00:00
claunia commented 2026-01-31 08:45:19 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Aug 25, 2025):

Check out this setting:

Image
@lhecker commented on GitHub (Aug 25, 2025): Check out this setting: <img width="2050" height="1044" alt="Image" src="https://github.com/user-attachments/assets/2ab40f22-d561-4fb3-9dd0-be85b6cea2ee" />
claunia commented 2026-01-31 08:45:19 +00:00
Author
Owner
Copy Link

@a-528 commented on GitHub (Aug 26, 2025):

That would be it. I didn't even think it could be an option. In my opinion it's a bad default as it goes against what most other shells do, just my two cents.

Than you for the quick response.

@a-528 commented on GitHub (Aug 26, 2025): That would be it. I didn't even think it could be an option. In my opinion it's a bad default as it goes against what most other shells do, just my two cents. Than you for the quick response.
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-Attention 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#23540
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?