You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "Paweł Janicki (JIRA)" <ji...@apache.org> on 2015/07/10 10:44:04 UTC

[jira] [Updated] (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:all-tabpanel ]

Paweł Janicki updated THRIFT-3238:
----------------------------------
    Attachment: 0001-Fix-TNamedPipeServer-can-be-interrupted-by-faulty-cl.patch

Including patch

> 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
>            Priority: Critical
>         Attachments: 0001-Fix-TNamedPipeServer-can-be-interrupted-by-faulty-cl.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.3.4#6332)