[ 
https://issues.apache.org/jira/browse/FLUME-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brock Noland updated FLUME-1552:
--------------------------------

          Description: 
{noformat}
012-09-09 16:59:25,454 (main) [ERROR -
org.apache.flume.channel.file.encryption.AESCTRNoPaddingProvider.getCipher(AESCTRNoPaddingProvider.java:137)]
Unable to load key using transformation: AES/CTR/NoPadding; Warning:
Maximum allowed key length = 128 with the available JCE security
policy files. Have you installed the JCE unlimited strength
jurisdiction policy files?
{noformat}

  was:

{noformat}
012-09-09 16:59:25,454 (main) [ERROR -
org.apache.flume.channel.file.encryption.AESCTRNoPaddingProvider.getCipher(AESCTRNoPaddingProvider.java:137)]
Unable to load key using transformation: AES/CTR/NoPadding; Warning:
Maximum allowed key length = 128 with the available JCE security
policy files. Have you installed the JCE unlimited strength
jurisdiction policy files?
{noformat}

    Affects Version/s: v1.3.0
        Fix Version/s: v1.3.0
    
> TestFileChannelEncryption fails without a high encryption policy file
> ---------------------------------------------------------------------
>
>                 Key: FLUME-1552
>                 URL: https://issues.apache.org/jira/browse/FLUME-1552
>             Project: Flume
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: v1.3.0
>            Reporter: Brock Noland
>            Assignee: Brock Noland
>            Priority: Critical
>             Fix For: v1.3.0
>
>
> {noformat}
> 012-09-09 16:59:25,454 (main) [ERROR -
> org.apache.flume.channel.file.encryption.AESCTRNoPaddingProvider.getCipher(AESCTRNoPaddingProvider.java:137)]
> Unable to load key using transformation: AES/CTR/NoPadding; Warning:
> Maximum allowed key length = 128 with the available JCE security
> policy files. Have you installed the JCE unlimited strength
> jurisdiction policy files?
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to