cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9633) Add ability to encrypt sstables
Date Wed, 23 Nov 2016 13:37:59 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690122#comment-15690122
] 

Stefan Podkowinski commented on CASSANDRA-9633:
-----------------------------------------------

I wonder if it would make sense to use a ParameterizedClass for the cassandra.yaml configuration.
The keystore based implementation is a great start, but there could be other ways to do this
and maybe we'll have someone contribute say a [Vault|https://www.vaultproject.io] based implementation
one day. Being able to configure a different class_name and parameters would make it easier
to integrate other solutions.

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

Mime
View raw message