Closed nicolaihenriksen closed 4 months ago
Have a look here: https://stackoverflow.com/questions/51546328/change-named-pipe-access-permissions
And then you can pass PipeSecurity into the NamedPipeServerOptions.
Have a look here....
Worked like a charm! Thank you very much.
And apparently I need to work on my "googling skills" 🤣
Hi
I have attached a small sample client/server app to illustrate what I am trying to achieve.
Basically, I would like the client application to be able to communicate with the server regardless of which elevation (normal user vs. admin user) the server was started with. I cannot seem to get this configured correctly, and perhaps it is not even possible.
If the server is not running elevated, then it does not matter if the client is elevated or not; both cases work. But it is a different story when the server is elevated. In the latter case it only works if the client is also elevated.
I assume I need to - somehow - use the
PipeSecurity
type to control this, but I cannot seem to figure out exactly how. Any help/guidance would be appreciated.The (typical) use case for this, is some devs in my team running their IDE as admin, and will be debugging a "server" application while simply starting a (non-elevated) client application on the side to communicate with it.
I am getting the following exception:
GrpcNamedPipesIssue.zip