[
https://issues.apache.org/jira/browse/STORM-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077131#comment-14077131
]
ASF GitHub Bot commented on STORM-348:
--------------------------------------
Github user RaghavendraNandagopal commented on the pull request:
https://github.com/apache/incubator-storm/pull/202#issuecomment-50416955
Hi Bobby,
I have made all the changes mentioned above and provided the comments for
specific questions.
I will look at the wrap/unwrap functionality within SASL and in the
meantime if you can review and provide your comments on the basic SASL
functionality.
Thanks,
Raghavendra Nandagopal
> (Security) Netty SASL Authentication
> ------------------------------------
>
> Key: STORM-348
> URL: https://issues.apache.org/jira/browse/STORM-348
> Project: Apache Storm (Incubating)
> Issue Type: Bug
> Reporter: Robert Joseph Evans
> Assignee: Raghavendra Nandagopal
> Labels: security
> Attachments: Storm-Netty Authentication.pdf
>
>
> Currently The Netty transport does no authentication at all. You can encrypt
> the tuples being sent, but that is a huge performance hit for many cases that
> do not need it. We should support simple SASL authentication when Netty
> first connects to an external process. We probably want to use something
> similar to what we do for ZK, and generate a random secret for each topology.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
