Return-Path: Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: (qmail 54325 invoked from network); 13 Jan 2011 16:44:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 Jan 2011 16:44:09 -0000 Received: (qmail 63552 invoked by uid 500); 13 Jan 2011 16:44:09 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 63152 invoked by uid 500); 13 Jan 2011 16:44:07 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 63136 invoked by uid 99); 13 Jan 2011 16:44:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jan 2011 16:44:06 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jan 2011 16:44:06 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id p0DGhjgB026118 for ; Thu, 13 Jan 2011 16:43:45 GMT Message-ID: <8578949.345701294937025639.JavaMail.jira@thor> Date: Thu, 13 Jan 2011 11:43:45 -0500 (EST) From: "Jeremy Hanna (JIRA)" To: commits@cassandra.apache.org Subject: [jira] Created: (CASSANDRA-1980) Add support for client-side encryption MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 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 Fix For: 0.8 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. - You can reply to this email to add a comment to the issue online.