You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Hindman (JIRA)" <ji...@apache.org> on 2014/01/15 20:23:47 UTC

[jira] [Commented] (MESOS-910) Add encryption support for master/slave/framework channels

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

Benjamin Hindman commented on MESOS-910:
----------------------------------------

Which "libhttp" did you have in mind?

> Add encryption support for master/slave/framework channels
> ----------------------------------------------------------
>
>                 Key: MESOS-910
>                 URL: https://issues.apache.org/jira/browse/MESOS-910
>             Project: Mesos
>          Issue Type: Story
>          Components: general, libprocess
>            Reporter: Adam B
>              Labels: encryption, security
>
> Currently all the messages that flow through the Mesos cluster are unencrypted making it possible for intruders to intercept and potentially control your task. We plan to add encryption support by adding SSL/TLS support to libprocess, the low-level communication library that Mesos uses for all network communication between Mesos components.
> As a first step, we should replace the hand-coded http code in libprocess with a standard library, like libhttp, ensuring that any mesos-custom code like routing remains. Then, transition to https should be easier.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)