You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since System.IO.Pipes.PipeSecurity is not supported on non windows Operating Systems, can we have another way for a less privileged NamedPipeClientStream to connect to a privileged user's pipe?
Currently, it seems that the only way is to do a chmod on the pipe file at /tmp/pipefile but no way to achieve this from code.
The text was updated successfully, but these errors were encountered:
Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.
This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.
Since System.IO.Pipes.PipeSecurity is not supported on non windows Operating Systems, can we have another way for a less privileged NamedPipeClientStream to connect to a privileged user's pipe?
Currently, it seems that the only way is to do a chmod on the pipe file at /tmp/pipefile but no way to achieve this from code.
The text was updated successfully, but these errors were encountered: