You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org> on 2007/11/10 01:06:50 UTC
[jira] Created: (HADOOP-2183) Change RPC to provide secure
communication
Change RPC to provide secure communication
------------------------------------------
Key: HADOOP-2183
URL: https://issues.apache.org/jira/browse/HADOOP-2183
Project: Hadoop
Issue Type: New Feature
Reporter: Tsz Wo (Nicholas), SZE
In the current version of RPC, there is no authentication or data protection. We propose to change the RPC framework, so that secure communication is possible.
The new RPC should:
- Compatible with current RPC
- Allow a pluggable security implementations (see HADOOP-1701)
- Support both secure and non-secure modes.
Here is a rough idea:
- Store security information (e.g. username, keys) in a ticket
- Use the ticket to establish a RPC connection
- Create secure sockets by the (subclass of) SocketFactory corresponding to the selected security implementations
- Send the data and RPC parameters with the secure sockets
When authentication is supported, the RPC callee should also initialize caller information during RPC setup and execute the RPC on the caller's behalf.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HADOOP-2183) Change RPC to provide secure
communication
Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz Wo (Nicholas), SZE resolved HADOOP-2183.
--------------------------------------------
Resolution: Duplicate
Created by accident: JIRE said that I hadn't login but the issue was created indeed.
> Change RPC to provide secure communication
> ------------------------------------------
>
> Key: HADOOP-2183
> URL: https://issues.apache.org/jira/browse/HADOOP-2183
> Project: Hadoop
> Issue Type: New Feature
> Reporter: Tsz Wo (Nicholas), SZE
>
> In the current version of RPC, there is no authentication or data protection. We propose to change the RPC framework, so that secure communication is possible.
> The new RPC should:
> - Compatible with current RPC
> - Allow a pluggable security implementations (see HADOOP-1701)
> - Support both secure and non-secure modes.
> Here is a rough idea:
> - Store security information (e.g. username, keys) in a ticket
> - Use the ticket to establish a RPC connection
> - Create secure sockets by the (subclass of) SocketFactory corresponding to the selected security implementations
> - Send the data and RPC parameters with the secure sockets
> When authentication is supported, the RPC callee should also initialize caller information during RPC setup and execute the RPC on the caller's behalf.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.