[
https://issues.apache.org/jira/browse/MESOS-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam B updated MESOS-910:
-------------------------
Description:
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, ensuring that any mesos custom code like routing remains.
Then, transition to https should be easier.
was:
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.
> 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, 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)
