You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jens Geyer (JIRA)" <ji...@apache.org> on 2019/02/28 07:44:00 UTC
[jira] [Resolved] (THRIFT-4813) NamedPipes may not work in all
cases
[ https://issues.apache.org/jira/browse/THRIFT-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jens Geyer resolved THRIFT-4813.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.13.0
PR committed
> NamedPipes may not work in all cases
> ------------------------------------
>
> Key: THRIFT-4813
> URL: https://issues.apache.org/jira/browse/THRIFT-4813
> Project: Thrift
> Issue Type: Bug
> Components: netstd - Library
> Reporter: Jens Geyer
> Assignee: Jens Geyer
> Priority: Major
> Fix For: 0.13.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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|https://github.com/dotnet/corefx/issues/24040]
> - [issue 34400 Have a mechanism for lower privileged user to connect to a privileged user's pipe|https://github.com/dotnet/corefx/issues/34400]
> - [issue 31190 System.IO.Pipes.AccessControl package does not work|https://github.com/dotnet/corefx/issues/31190]
> Also interesting in this context is [issue 30170|https://github.com/dotnet/corefx/issues/30170] which finally got closed and is continued in issue )31190 (listed above).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)