You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2016/01/08 01:30:39 UTC

[jira] [Updated] (HBASE-13506) AES-GCM cipher support where available

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

Andrew Purtell updated HBASE-13506:
-----------------------------------
    Fix Version/s:     (was: 1.0.4)
                       (was: 0.98.17)
                       (was: 1.1.4)
                       (was: 1.2.1)
                   0.98.18

> AES-GCM cipher support where available
> --------------------------------------
>
>                 Key: HBASE-13506
>                 URL: https://issues.apache.org/jira/browse/HBASE-13506
>             Project: HBase
>          Issue Type: Sub-task
>          Components: encryption, security
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>             Fix For: 2.0.0, 1.3.0, 0.98.18
>
>
> The initial encryption drop only had AES-CTR support because authenticated modes such as GCM are only available in Java 7 and up, and our trunk at the time was targeted at Java 6. However we can optionally use AES-GCM cipher support where available. For HBase 1.0 and up, Java 7 is now the minimum so use of AES-GCM can go in directly. It's probably possible to add support in 0.98 too using reflection for cipher object initialization. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)