[
https://issues.apache.org/jira/browse/SPARK-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372394#comment-14372394
]
Marcelo Vanzin commented on SPARK-6229:
---------------------------------------
Yes, and that's actually what I'm proposing. Maybe not exactly in
TransportContext, but somewhere inside the network library.
But if I understand what you and Aaron are proposing, you seem to want to
expose the actual {{ChannelPipeline}} to these call sites, or some other method
that allows clients to insert things into the pipeline. Sorry if I'm
misunderstanding something.
> Support SASL encryption in network/common module
> ------------------------------------------------
>
> Key: SPARK-6229
> URL: https://issues.apache.org/jira/browse/SPARK-6229
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Reporter: Marcelo Vanzin
>
> After SASL support has been added to network/common, supporting encryption
> should be rather simple. Encryption is supported for DIGEST-MD5 and GSSAPI.
> Since the latter requires a valid kerberos login to work (and so doesn't
> really work with executors), encryption would require the use of DIGEST-MD5.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
