spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcelo Vanzin (JIRA)" <>
Subject [jira] [Commented] (SPARK-6229) Support SASL encryption in network/common module
Date Fri, 10 Apr 2015 02:34:12 GMT


Marcelo Vanzin commented on SPARK-6229:

I'm not sure the constructor is the best place for that argument, but I'm sure that part can
be figured out in code review. :-) The main issue I see is again because SASL and SSL work
differently. Your {{initChannel}} doesn't work for SASL, at least not for the current implementation,
because, on the server side, it's built on top of the existing RPC interface (i.e. {{RpcHandler}}),
not on top of the raw netty handler.

Not to say that is not fixable. I'm just saying that I'm not seeing a lot of value in trying
to define this {{TransportEncryptionHandler}} type; it's not a handler in the netty sense
of the word, and it's basically just giving some arbitrary code access to the underlying channel
(so that it can set up handlers and so on), so the name seems misleading to start with.

> Support SASL encryption in network/common module
> ------------------------------------------------
>                 Key: SPARK-6229
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message