Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 011221910E for ; Tue, 19 Apr 2016 16:03:27 +0000 (UTC) Received: (qmail 43339 invoked by uid 500); 19 Apr 2016 16:03:26 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 43306 invoked by uid 500); 19 Apr 2016 16:03:26 -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 43170 invoked by uid 99); 19 Apr 2016 16:03:26 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Apr 2016 16:03:26 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id BB73A2C1F75 for ; Tue, 19 Apr 2016 16:03:25 +0000 (UTC) Date: Tue, 19 Apr 2016 16:03:25 +0000 (UTC) From: "Jason Brown (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-9633) Add ability to encrypt sstables MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-9633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15248041#comment-15248041 ] Jason Brown commented on CASSANDRA-9633: ---------------------------------------- [~iamaleksey] Please :) > Add ability to encrypt sstables > ------------------------------- > > Key: CASSANDRA-9633 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9633 > Project: Cassandra > Issue Type: New Feature > Reporter: Jason Brown > Assignee: Jason Brown > Labels: encryption, security, sstable > Fix For: 3.x > > > Add option to allow encrypting of sstables. > I have a version of this functionality built on cassandra 2.0 that piggy-backs on the existing sstable compression functionality and ICompressor interface (similar in nature to what DataStax Enterprise does). However, if we're adding the feature to the main OSS product, I'm not sure if we want to use the pluggable compression framework or if it's worth investigating a different path. I think there's a lot of upside in reusing the sstable compression scheme, but perhaps add a new component in cqlsh for table encryption and a corresponding field in CFMD. > Encryption configuration in the yaml can use the same mechanism as CASSANDRA-6018 (which is currently pending internal review). -- This message was sent by Atlassian JIRA (v6.3.4#6332)