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/07/03 12:54:00 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=16072387#comment-16072387 ] 

ASF GitHub Bot commented on ROCKETMQ-28:
----------------------------------------

Github user coveralls commented on the issue:

    https://github.com/apache/incubator-rocketmq/pull/118
  
    
    [![Coverage Status](https://coveralls.io/builds/12231167/badge)](https://coveralls.io/builds/12231167)
    
    Coverage increased (+0.3%) to 38.725% when pulling **0ca60db50aec2abc3ad3c3ea4a92e838a7579734 on lizhanhui:tls** into **c4a3e0c1325e67aec76aa94e9ade3a6ea1b682d2 on apache:develop**.



> 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)