You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "James E. King, III (JIRA)" <ji...@apache.org> on 2017/09/22 18:29:00 UTC
[jira] [Commented] (THRIFT-3238) Fix TNamedPipeServer can be
interrupted by faulty client
[ https://issues.apache.org/jira/browse/THRIFT-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16176887#comment-16176887 ]
James E. King, III commented on THRIFT-3238:
--------------------------------------------
THRIFT-4283 might be relevant here - any overlap?
> Fix TNamedPipeServer can be interrupted by faulty client
> --------------------------------------------------------
>
> Key: THRIFT-3238
> URL: https://issues.apache.org/jira/browse/THRIFT-3238
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Library
> Affects Versions: 0.9.2
> Environment: Windows
> Reporter: Paweł Janicki
> Attachments: 0001-Fix-TNamedPipeServer-can-be-interrupted-by-faulty-cl.patch, 0002-THRIFT-3238.-cpp-Fix-TNamedPipeServer-can-be-interru.patch
>
>
> A faulty or hostile client can cause TNamedPipeServer to be interrupted and return from serve(). The client that causes such effect just needs to open and immediately close TPipe transport.
> Caused by not handling some NamedPipe error codes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)