[
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)
