Paul Higinbotham

Unfortunately, I am not able to repro this since I cannot get a set-up with gMSA accounts. But I looked at the code and PowerShell will only write the transcript...

This is very interesting, and I suspect it works because SecretManagement is being run in a PowerShell job, which in turn runs in a child process. So whatever breaks transcripts/information...

Closing this issue as I feel it needs to be investigated by PowerShell team, since it is breaking PowerShell transcripts/data streams, and it has been transferred to PowerShell repository.

Oh, I see this is the same PR just transferred. Re-opening.

Windows cleans up all resources when a process exits, including named pipes, but it looks like we can't rely on this for Linux systems. For Windows PowerShell we were using...

WG-Remoting Re-opening issue since it appears the fix isn't working on all platforms. One thing we can consider is making the named pipe listener opt-in. That way most powershell instances...

@PowerShell/powershell-committee We make a best effort to clean up listener named pipes on process exit, but it is not foolproof depending on how the process is exited. Windows cleans up...

The listener is per process and not per runspace, so I didn't think it made sense to include it in InitialSessionState. Disabling the listener should probably just be an API...

Again, I feel the listener state should not be part of `InitialSessionState` since it has nothing to do with runspace sessions. A public API is sufficient for opting out of...

@PowerShell/powershell-committee The PowerShell committee discussed this today, and regarding whether to make this named pipe connection feature `opt-in` or `opt-out`, we agree with @iSazonov that `opt-in` is the best solution....