NamedPipes may not work in all cases

The classes provided in current net standard to deal with PipeSecurity are broken, they simply do not work. Hence, in some cases a connection cannot be established. A possible scenario would be between a normal client and an elevated server (think of an UI to control a service process).

Ticket references

• issue 24040 NamedPipeServerStream: Provide support for WRITE_DAC
• issue 34400 Have a mechanism for lower privileged user to connect to a privileged user's pipe
• issue 31190 System.IO.Pipes.AccessControl package does not work

Also interesting in this context is issue 30170 which finally got closed and is continued in issue )31190 (listed above).