EPERM for clients connecting via named pipe

[computerquip-streamlabs]

Platform: Windows 10
Node: 8.9.4
Subsystem: Net

We sometimes must launch our application as administrator. When we do, clients attempting to connect to our application over a named pipe (which was created during a call to server.listen()) that are not run as administrator are no longer able to connect. We have no known way of change permissions of our handle to make sure it can be written to from a non-administrator process.

[gireeshpunathil]

we recently added a chmod facility for pipes through libuv/libuv#1386 in libuv, though I am not sure whether we have made an abstraction around it in node, and whether it covers windows platform.
/cc @bzoz

[computerquip-streamlabs]

There appears to be code there for Windows but I don't see a way to use it from Node.

[bzoz]

Yep, we need to add mappings to Node. I'll do this.

[bzoz]

I've gave it a shot (JaneaSystems@74c72e0), but this does not work. Node client fails with ENOTCONN when trying to read from pipe, maybe because of this line: https://github.com/libuv/libuv/blob/88c2af0e65ed49ff599f5afd4bf952ecdfab4594/src/win/pipe.c#L2122.