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

Eric Evans commented on CASSANDRA-4239:
---------------------------------------

bq. ...the problem is reusing is that TTransport doesn't expose hostname and 
port. SST in the core uses CliSessionState to get around the problem.

There is always an instance of this factory, couldn't you create a ctor that 
accepted arguments for hostname, protocol, cipher suites, etc (including one 
that accepted a list of hosts to shuffle through, for stress)?

bq. Currently to use the transport factory the user has to use -tr 
org.apache.cassandra.cli.transport.SSLTransportFactory in the clients 
(including stress tool)...

How many other transports other than this, and the default does stress need?  
Couldn't the argument simply be -ssl or something, negating the need to supply 
the entire class name?
                
> 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: Jason Brown
>            Priority: Minor
>             Fix For: 1.2.1
>
>         Attachments: 
> 0001-CASSANDRA-4239-Support-Thrift-SSL-socket-both-to-the.patch, 
> 0001-CASSANDRA-4239-v3.patch, 0002-CASSANDRA-4239-Support-Thrift-SSL.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to