[
https://issues.apache.org/jira/browse/CASSANDRA-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15105206#comment-15105206
]
Branimir Lambov commented on CASSANDRA-6018:
--------------------------------------------
Two of the points above don't appear to be addressed and I believe they cause
unwanted behaviour changes:
- please use {{tolerateTruncation}} in {{CommitLogReplayer}} instead of the
[AND-ed
value|https://github.com/jasobrown/cassandra/blob/7526af73ebc461d2db50ef52b89985212826e6d7/src/java/org/apache/cassandra/db/commitlog/CommitLogReplayer.java#L390],
which makes us less tolerant than we want to be for pre-2.1 recycled segments;
- [OR in catching
{{SegmentReadException}}|https://github.com/jasobrown/cassandra/commit/7526af73ebc461d2db50ef52b89985212826e6d7#diff-4c3a8240a441cef90e68dddd0246ee64R105]
should be an AND.
> 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)
