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

Narayanan Venkateswaran edited comment on HADOOP-15980 at 7/27/22 3:33 AM:
---------------------------------------------------------------------------

As a follow-up to my previous work, I have,
 # Split the files Server.java and Client.java to reduce clutter.
 # Parameterized the RPC unit tests to work with SSL on, instead of duplicating 
them as I had done earlier.
 # Attaching a PDF document that describes the changes that have been done in 
detail to help reviewers / readers of the patch. Please do read this document 
to understand the changes in more detail.


was (Author: vnhive):
As a follow-up to my previous work, I have,

 
 # Split the files Server.java and Client.java to reduce clutter.
 # Parameterized the RPC unit tests to work with SSL on, instead of duplicating 
them as I had done earlier.
 # Attaching a PDF document that describes the changes that have been done in 
detail to help reviewers / readers of the patch. Please do read this document 
to understand the changes in more detail.

 

 

> Enable TLS in RPC client/server
> -------------------------------
>
>                 Key: HADOOP-15980
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15980
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: ipc, security
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 5h 40m
>  Remaining Estimate: 0h
>
> Once the RPC client and server can be configured to use Netty, the TLS engine 
> can be added to the channel pipeline.  The server should allow QoS-like 
> functionality to determine if TLS is mandatory or optional for a client.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to