Hey Patrick,

Yes, I will open a Jira tomorrow... For now my implementation is a basic
SSL implementation for the TransportServer and TransportClient.. I will
type up the design and at the same time look at the Hadoop impl for
possible improvements... Cheers!

Jeff


On Sun, Mar 8, 2015 at 5:51 PM, Patrick Wendell <[email protected]> wrote:

> I think that yes, longer term we want to have encryption of all
> communicated data. However Jeff, can you open a JIRA to discuss the
> design before opening a pull request (it's fine to link to a WIP
> branch if you'd like)? I'd like to better understand the performance
> and operational complexity of using SSL for this in comparison with
> alternatives. It would also be good to look at how the Hadoop
> encryption works for their shuffle service, in terms of the design
> decisions made there.
>
> - Patrick
>
> On Sun, Mar 8, 2015 at 5:42 PM, Jeff Turpin <[email protected]> wrote:
> > I have already written most of the code, just finishing up the unit tests
> > right now...
> >
> > Jeff
> >
> >
> > On Sun, Mar 8, 2015 at 5:39 PM, Andrew Ash <[email protected]> wrote:
> >
> >> I'm interested in seeing this data transfer occurring over encrypted
> >> communication channels as well.  Many customers require that all network
> >> transfer occur encrypted to prevent the "soft underbelly" that's often
> >> found inside a corporate network.
> >>
> >> On Fri, Mar 6, 2015 at 4:20 PM, turp1twin <[email protected]> wrote:
> >>
> >>> Is there a plan to implement SSL support for the Block Transfer Service
> >>> (specifically, the NettyBlockTransferService implementation)? I can
> >>> volunteer if needed...
> >>>
> >>> Jeff
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> View this message in context:
> >>>
> http://apache-spark-developers-list.1001551.n3.nabble.com/Block-Transfer-Service-encryption-support-tp10934.html
> >>> Sent from the Apache Spark Developers List mailing list archive at
> >>> Nabble.com.
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [email protected]
> >>> For additional commands, e-mail: [email protected]
> >>>
> >>>
> >>
>

Reply via email to