[
https://issues.apache.org/jira/browse/ROCKETMQ-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047632#comment-16047632
]
ASF GitHub Bot commented on ROCKETMQ-28:
----------------------------------------
GitHub user lizhanhui opened a pull request:
https://github.com/apache/incubator-rocketmq/pull/118
[ROCKETMQ-28] Encrypt transmission layer.
JIRA issue is [here](https://issues.apache.org/jira/browse/ROCKETMQ-28)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lizhanhui/incubator-rocketmq tls
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-rocketmq/pull/118.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #118
----
commit 66b5c7241651f54f7d483f99278cda537b5e4aac
Author: Li Zhanhui <[email protected]>
Date: 2017-06-13T09:15:54Z
Add TLS
----
> Transportation Layer Security
> -----------------------------
>
> Key: ROCKETMQ-28
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-28
> Project: Apache RocketMQ
> Issue Type: New Feature
> Components: rocketmq-remoting
> Reporter: Zhanhui Li
> Assignee: Zhanhui Li
> Fix For: 4.2.0-incubating
>
>
> RocketMQ delivers data in clear text for now, which requires internal network
> environment. As use scenarios expand, end-to-end security is in bad need.
> This issue is to introduce features making RocketMQ security for various use
> cases and sacrificing as few as possible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
