You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/04/11 17:38:05 UTC

[jira] [Resolved] (CASSANDRA-1980) Add support for client-side encryption

     [ https://issues.apache.org/jira/browse/CASSANDRA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-1980.
---------------------------------------

       Resolution: Later
    Fix Version/s:     (was: 0.8)

as with CASSANDRA-974, let's table this until we see how the CQL transport evolves

> Add support for client-side encryption
> --------------------------------------
>
>                 Key: CASSANDRA-1980
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1980
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jeremy Hanna
>
> With thrift-106 in place coming in thrift version 0.6, it will be necessary to add a way for making the server aware of that.  We could allow the option in the server configuration (cassandra.yaml) to use encrypted or non-encrypted client connections.  However if they choose encrypted, the only clients able to connect would be java clients at this point.  It might be better to take some more time and look at how to enable accepting both encrypted and unencrypted connections at the same time.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira