You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2013/06/13 07:46:22 UTC

[jira] [Commented] (FLUME-997) Support secure transport mechanism

    [ https://issues.apache.org/jira/browse/FLUME-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681927#comment-13681927 ] 

Mike Percy commented on FLUME-997:
----------------------------------

+1

Let's get this into Flume 1.4. I have a couple more points of feedback but I will file those in a follow-up JIRA:

1. If the server is configured for SSL but the keystore isn't there, the service should not start.
2. We should fall back to the default behavior of the X509 TrustManagerFactory if there is no trust store specified by passing a null KeyStore, no need to look in the classpath for cacerts.

                
> Support secure transport mechanism
> ----------------------------------
>
>                 Key: FLUME-997
>                 URL: https://issues.apache.org/jira/browse/FLUME-997
>             Project: Flume
>          Issue Type: New Feature
>    Affects Versions: v1.0.0
>            Reporter: Mike Percy
>              Labels: security
>             Fix For: v1.4.0
>
>         Attachments: FLUME-997-1.patch, FLUME-997-2.patch, FLUME-997-3.patch
>
>
> Flume needs support for a secure network transport protocol. See AVRO-898 for a patch that made it into Avro 1.6.0 that allows us to do this relatively easily.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira