[
https://issues.apache.org/jira/browse/SPARK-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363898#comment-14363898
]
Marcelo Vanzin commented on SPARK-6229:
---------------------------------------
HI [~adav], thanks for the comments. I'm fine with either solution. I'm a
little more partial to my solution because I already have an implementation of
it in Hive :-), and in general I prefer users to configure things using
configuration values instead of having to write code. Especially because if
they mess up the channel pipeline, weird things can happen.
SSL + SASL auth can still be supported with my approach: just do not configure
encryption for SASL. You could even enable both for encryption, but all you'd
get is more CPU / memory being used. :-)
> Support 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]
