[
https://issues.apache.org/jira/browse/CASSANDRA-12945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690362#comment-15690362
]
Jason Brown edited comment on CASSANDRA-12945 at 11/23/16 3:12 PM:
-------------------------------------------------------------------
The unit tests current break as I think I created the current test key with
AES256, which, I believe, is only unlocked with the updated JCE policies (as
you correctly point out). I like this solution, so if you want to create a
patch/branch, I'll review and we can get this one done.
was (Author: jasobrown):
The unit tests current break as I think I created the current test key with
AES256, which, I believe, is only unlock with the updated JCE policies (as you
correctly point out). I like this solution, so if you want to create a
patch/branch, I'll review and we can get this one done.
> Resolve unit testing without JCE security libraries installed
> -------------------------------------------------------------
>
> Key: CASSANDRA-12945
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12945
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jason Brown
> Assignee: Jason Brown
>
> Running unit tests can fail on encryption-related tests if you don't have
> something like the Oracle JCE libraries installed in your jdk. We can't
> redistribute the Oracle JCE due to export laws, then we'd need to somehow get
> it into the <jdk>/jre/lib/security.
> One possibility is to ignore encryption-related tests if there is no
> encryption lib available. Another is to ship something like bouncycastle.jar
> in the test directory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
