Closed as not planned
Description
Version
16.15.1
Platform
Windows 11
Subsystem
net
What steps will reproduce the bug?
The API for creating a named pipe in Windows does not allow setting permissions of the named pipe and by default pipes are readable by everyone. This makes secure programming very difficult.
How often does it reproduce? Is there a required condition?
Always.
What is the expected behavior?
No response
What do you see instead?
Either default permissions should be set to current user only or an API should be provided to set the permissions.
Additional information
No response