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 2021/04/01 11:33:00 UTC
[jira] [Comment Edited] (THRIFT-5388) Open Named Pipes API to pass
additional flags
[ https://issues.apache.org/jira/browse/THRIFT-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313098#comment-17313098 ]
Jens Geyer edited comment on THRIFT-5388 at 4/1/21, 11:32 AM:
--------------------------------------------------------------
[~christmasliu], given you get what you want. What flag would you pass exactly to prevent the server from doing that? I probably overlook something but there is no single documented flag that comes in any way close to what you said you will do.
PS: If this is really a security issue, there is a well defined process for that.
was (Author: jensg):
[~christmasliu], given you get what you want. What flag would you pass exactly to prevent the server from doing that? I probably overlook something but there is no single docuemnted flag that commes in any way close to what you said you will do.
> Open Named Pipes API to pass additional flags
> ---------------------------------------------
>
> Key: THRIFT-5388
> URL: https://issues.apache.org/jira/browse/THRIFT-5388
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Library
> Reporter: Steven
> Priority: Major
>
> In current codes "lib\cpp\src\thrift\transport\TPipe.cpp", the flags to connect the named pipe is always FILE_FLAG_OVERLAPPED. It is not possible to set more security flags to avoid the named pipe server misuse the named pipe client's identify by "https://docs.microsoft.com/en-us/windows/win32/api/namedpipeapi/nf-namedpipeapi-impersonatenamedpipeclient". Could we provide the API to set these flags? Thanks.
> Codes in "TPipe::open()" are listed below:
> DWORD flags = FILE_FLAG_OVERLAPPED;
> hPipe.reset(CreateFileA(pipename_.c_str(), GENERIC_READ | GENERIC_WRITE, 0, nullptr, OPEN_EXISTING, flags, nullptr));
--
This message was sent by Atlassian Jira
(v8.3.4#803005)