[
https://issues.apache.org/jira/browse/CASSANDRA-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15094080#comment-15094080
]
Branimir Lambov commented on CASSANDRA-6018:
--------------------------------------------
Sorry, {{CommitLogReplayer}} still does {{tolerateErrorsInSection &= end ==
reader.length() || end < 0;}} for uncompressed segments.
It's better to not do anything there as compression / decryption should have
blown up by then (and the {{CommitLogUpgradeTest}} will verify that it does).
We should also add an encrypted log to {{CommitLogUpgradeTest}}.
> Add option to encrypt commitlog
> --------------------------------
>
> Key: CASSANDRA-6018
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6018
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jason Brown
> Assignee: Jason Brown
> Labels: commit_log, encryption, security
> Fix For: 3.x
>
>
> We are going to start using cassandra for a billing system, and while I can
> encrypt sstables at rest (via Datastax Enterprise), commit logs are more or
> less plain text. Thus, an attacker would be able to easily read, for example,
> credit card numbers in the clear text commit log (if the calling app does not
> encrypt the data itself before sending it to cassandra).
> I want to allow the option of encrypting the commit logs, most likely
> controlled by a property in the yaml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
