Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 918CA200C49 for ; Fri, 17 Mar 2017 19:23:48 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 901BD160B80; Fri, 17 Mar 2017 18:23:48 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id DA412160B70 for ; Fri, 17 Mar 2017 19:23:47 +0100 (CET) Received: (qmail 27665 invoked by uid 500); 17 Mar 2017 18:23:47 -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 27652 invoked by uid 99); 17 Mar 2017 18:23:47 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Mar 2017 18:23:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 8220ACAC45 for ; Fri, 17 Mar 2017 18:23:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.451 X-Spam-Level: * X-Spam-Status: No, score=1.451 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id ob_GdgpEvu5p for ; Fri, 17 Mar 2017 18:23:45 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id CA1AC5F473 for ; Fri, 17 Mar 2017 18:23:44 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 2AA57E0C13 for ; Fri, 17 Mar 2017 18:23:43 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3A7C1254D5 for ; Fri, 17 Mar 2017 18:23:42 +0000 (UTC) Date: Fri, 17 Mar 2017 18:23:42 +0000 (UTC) From: "Vincenzo Melandri (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (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 archived-at: Fri, 17 Mar 2017 18:23:48 -0000 [ https://issues.apache.org/jira/browse/CASSANDRA-9633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930422#comment-15930422 ] Vincenzo Melandri edited comment on CASSANDRA-9633 at 3/17/17 6:23 PM: ----------------------------------------------------------------------- Hello, just to bump this up. I care about this feature :) Is there any movement here, is this going to be in any next release soon? Or maybe can I pitch in? (0 background in cassandra development, but maybe I could help, worst case scenario with testing..) was (Author: vmelandri): Hello, just to bump this up. I care about this feature :) Is there any movement here, is this going to be in any next release soon? Or maybe can I pitch in? > 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: 4.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.15#6346)