You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@rocketmq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/06/05 09:15:04 UTC
[jira] [Commented] (ROCKETMQ-28) Transportation Layer Security
[ https://issues.apache.org/jira/browse/ROCKETMQ-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036703#comment-16036703 ]
ASF GitHub Bot commented on ROCKETMQ-28:
----------------------------------------
GitHub user lizhanhui opened a pull request:
https://github.com/apache/incubator-rocketmq/pull/111
[ROCKETMQ-28] Add TLS support to provide end-2-end security
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lizhanhui/incubator-rocketmq ROCKETMQ-28
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-rocketmq/pull/111.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 #111
----
commit 6fcb64920748ffeb88d2035ee2885c6dd90db2cc
Author: Li Zhanhui <li...@gmail.com>
Date: 2017-06-05T08:37:36Z
Add TLS to provide end-2-end security
----
> 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: Stevens Chew
> 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.3.15#6346)