You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2015/11/18 00:00:12 UTC

[jira] [Commented] (HADOOP-12579) Deprecate and remove WriteableRPCEngine

    [ https://issues.apache.org/jira/browse/HADOOP-12579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009784#comment-15009784 ] 

Chris Nauroth commented on HADOOP-12579:
----------------------------------------

+1 for the proposal.

{{WritableRpcEngine}} can be a source of confusion for new development too if you're creating a new RPC service.  The current code assumes {{WritableRpcEngine}} as the default.  If you don't explicitly bind your new service to {{ProtobufRpcEngine}}, then the resulting error messages are unclear.

> Deprecate and remove WriteableRPCEngine
> ---------------------------------------
>
>                 Key: HADOOP-12579
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12579
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Haohui Mai
>
> The {{WriteableRPCEninge}} depends on Java's serialization mechanisms for RPC requests. Without proper checks, it has be shown that it can lead to security vulnerabilities such as remote code execution (e.g., COLLECTIONS-580, HADOOP-12577).
> The current implementation has migrated from {{WriteableRPCEngine}} to {{ProtobufRPCEngine}} now. This jira proposes to deprecate {{WriteableRPCEngine}} in branch-2 and to remove it in trunk.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)