You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Blake Eggleston (JIRA)" <ji...@apache.org> on 2016/02/09 23:23:18 UTC
[jira] [Commented] (CASSANDRA-11040) Encrypted hints
[ https://issues.apache.org/jira/browse/CASSANDRA-11040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139885#comment-15139885 ]
Blake Eggleston commented on CASSANDRA-11040:
---------------------------------------------
Everything looks good functionally, although the yaml defaults/docs could be improved a bit.
# AES is a good default, but it's not the only cipher supported by java, so I'd remove the second sentence from the first paragraph. I was able to startup with RC2, and DES and Blowfish should work fine as well.
# Although you *should* use the unlimited JCE policy if possible, everything will work fine without it. I'd reword the second paragraph to strongly recommend, but not require it.
# Could we make the default key alias and keystore location something not test related?
# The comment about CBC requiring a 16 byte IV applies to AES, but not all ciphers.
Also, could you post the cassci job results?
> Encrypted hints
> ---------------
>
> Key: CASSANDRA-11040
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11040
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jason Brown
> Assignee: Jason Brown
> Priority: Minor
> Labels: encryption, hints, security
>
> When users enable system-wide encryption (which includes commit logs, CASSANDRA-6018), we need to encrypt other assets, as well. Hence, let's encrypt hints.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)