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

Brandon Williams commented on CASSANDRA-4239:
---------------------------------------------

One problem we're going to have here is specifying client encryption options, 
since unfortunately when we added internode encryption we used some names that 
are a bit generic:

{noformat}
encryption_options:
    internode_encryption: none
    keystore: conf/.keystore
    keystore_password: cassandra
    truststore: conf/.truststore
    truststore_password: cassandra
    # More advanced defaults below:
    # protocol: TLS
    # algorithm: SunX509
    # store_type: JKS
    # cipher_suites: [TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA]
{noformat}

If we can get by with using the same keystore/truststore for clients as we do 
nodes, then this isn't a big deal, otherwise we're going to either have some 
pretty confusing options for 1.1, or have to push this to 1.2 to reorg.
                
> Support Thrift SSL socket
> -------------------------
>
>                 Key: CASSANDRA-4239
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4239
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API
>            Reporter: Jonathan Ellis
>            Assignee: Brandon Williams
>            Priority: Minor
>             Fix For: 1.1.2
>
>
> Thrift has supported SSL encryption for a while now (THRIFT-106); we should 
> allow configuring that in cassandra.yaml

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to