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

Powershell and command line used in the pipe "|" inconsistent results #17178

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

Originally created by @ljxqc on GitHub (Apr 7, 2022).

Windows Terminal version

1.12.10733.0

Windows build number

10.0.22593.1

Other Software

openssl 3.0.1

Steps to reproduce

Run the openssl command to obtain the web remote certificate(use pipe "|")：

openssl s_client -connect www.baidu.com:443 -servername www.baidu.com | openssl x509 -pubkey -nout | openssl rsa -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64

Expected Behavior

image

Actual Behavior

image

Originally created by @ljxqc on GitHub (Apr 7, 2022). ### Windows Terminal version 1.12.10733.0 ### Windows build number 10.0.22593.1 ### Other Software openssl 3.0.1 ### Steps to reproduce Run the openssl command to obtain the web remote certificate(use pipe "|")： > openssl s_client -connect www.baidu.com:443 -servername www.baidu.com | openssl x509 -pubkey -nout | openssl rsa -pubin -outform der | openssl dgst -sha256 -binary | openssl enc -base64 ### Expected Behavior ![image](https://user-images.githubusercontent.com/72794384/162246162-37f98b43-0333-473c-bb9d-89583e12f9eb.png) ### Actual Behavior ![image](https://user-images.githubusercontent.com/72794384/162246229-65e8068d-d672-456f-ba91-4a57fe5e6f7a.png)
claunia added the Issue-BugResolution-ExternalNeeds-Tag-Fix labels 2026-01-31 05:34:26 +00:00
claunia commented 2026-01-31 05:34:27 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 7, 2022):

PowerShell doesn't work like traditional shells and doesn't support "raw pipes" between processes like under UNIX (or cmd.exe). When you write a pipe | in PowerShell, it'll transform the output into objects and give it some meaning.

So for instance if you write this:

Get-ChildItem | Get-Content

Get-ChildItem returns a Object[], where each Object is actually a instance of DirectoryInfo. It doesn't transmit "text" at all!

Since PowerShell only supports objects and not raw text, it's thus forced to turn any and all application output in some form of object. For instance try running this:

(openssl version).GetType()

Since version prints a single line, PowerShell will turn it into a String object.

If you run something that prints many lines it'll turn it into an array of Strings:

(openssl genrsa).GetType()

This means your openssl dgst -sha256 -binary will not work, because it outputs binary data, which isn't valid UTF8 text. PowerShell only accepts valid Strings though and will thus discard some of your raw binary data. I think you should check out https://github.com/PowerShell/PowerShell/issues/1908. 🙂

I'm personally not particularly happy about this behavior either, but it definitely isn't a fault in Windows Terminal and a fix seems to be in the near term roadmap.

/dup https://github.com/PowerShell/PowerShell/issues/1908

@lhecker commented on GitHub (Apr 7, 2022): PowerShell doesn't work like traditional shells and doesn't support "raw pipes" between processes like under UNIX (or cmd.exe). When you write a pipe `|` in PowerShell, it'll transform the output into objects and give it some meaning. So for instance if you write this: ```pwsh Get-ChildItem | Get-Content ``` `Get-ChildItem` returns a `Object[]`, where each `Object` is actually a instance of `DirectoryInfo`. It doesn't transmit "text" at all! Since PowerShell only supports objects and not raw text, it's thus forced to turn any and all application output in some form of object. For instance try running this: ``` (openssl version).GetType() ``` Since `version` prints a single line, PowerShell will turn it into a `String` object. If you run something that prints many lines it'll turn it into an array of `String`s: ``` (openssl genrsa).GetType() ``` This means your `openssl dgst -sha256 -binary` will not work, because it outputs binary data, which isn't valid UTF8 text. PowerShell only accepts valid `String`s though and will thus discard some of your raw binary data. I think you should check out https://github.com/PowerShell/PowerShell/issues/1908. 🙂 I'm personally not particularly happy about this behavior either, but it definitely isn't a fault in Windows Terminal and a fix seems to be in the near term roadmap. /dup https://github.com/PowerShell/PowerShell/issues/1908
claunia commented 2026-01-31 05:34:28 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 7, 2022):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@ghost commented on GitHub (Apr 7, 2022): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!
claunia commented 2026-01-31 05:34:28 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 7, 2022):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@ghost commented on GitHub (Apr 7, 2022): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!
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-Tag-Fix Resolution-External
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#17178
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?