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

2018-03-01 Thread stack (JIRA)

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

stack updated HBASE-13506:
--
Fix Version/s: (was: 2.0.0)

> 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
>Priority: Major
>
> 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
(v7.6.3#76005)


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

2016-06-16 Thread Andrew Purtell (JIRA)

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

Andrew Purtell updated HBASE-13506:
---
Assignee: (was: Andrew Purtell)

> 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
> Fix For: 2.0.0
>
>
> 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)


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

2016-06-16 Thread Andrew Purtell (JIRA)

 [ 
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: 0.98.21)
   (was: 1.3.0)

> 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
>
>
> 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)


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

2016-06-07 Thread Andrew Purtell (JIRA)

 [ 
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: 0.98.20)
   0.98.21

> 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.21
>
>
> 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)


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

2016-04-22 Thread Andrew Purtell (JIRA)

 [ 
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: 0.98.19)
   0.98.20

> 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.20
>
>
> 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)


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

2016-03-18 Thread Andrew Purtell (JIRA)

 [ 
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: 0.98.18)
   0.98.19

> 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.19
>
>
> 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)


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

2016-01-07 Thread Andrew Purtell (JIRA)

 [ 
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)


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

2015-11-03 Thread Andrew Purtell (JIRA)

 [ 
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.3)
   1.0.4

> 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, 1.2.1, 1.1.4, 0.98.17, 1.0.4
>
>
> 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)


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

2015-10-31 Thread Andrew Purtell (JIRA)

 [ 
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: 0.98.16)
   0.98.17

> 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, 1.2.1, 1.0.3, 1.1.4, 0.98.17
>
>
> 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)


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

2015-10-01 Thread Andrew Purtell (JIRA)

 [ 
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: 0.98.15)
   0.98.16

> 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, 1.2.1, 1.0.3, 0.98.16, 1.1.4
>
>
> 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)


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

2015-09-29 Thread Nick Dimiduk (JIRA)

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

Nick Dimiduk updated HBASE-13506:
-
Fix Version/s: (was: 1.1.3)
   1.1.4

> 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.15, 1.2.1, 1.0.3, 1.1.4
>
>
> 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)


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

2015-08-13 Thread Andrew Purtell (JIRA)

 [ 
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: 0.98.14)
   0.98.15

 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.15, 1.2.1, 1.0.3, 1.1.3


 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)


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

2015-08-04 Thread Nick Dimiduk (JIRA)

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

Nick Dimiduk updated HBASE-13506:
-
Fix Version/s: (was: 1.1.2)
   1.1.3

 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, 0.98.14, 1.3.0, 1.2.1, 1.0.3, 1.1.3


 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)


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

2015-07-02 Thread Enis Soztutar (JIRA)

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

Enis Soztutar updated HBASE-13506:
--
Fix Version/s: (was: 1.0.2)
   1.0.3

 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, 0.98.14, 1.1.2, 1.3.0, 1.2.1, 1.0.3


 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)


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

2015-07-02 Thread Sean Busbey (JIRA)

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

Sean Busbey updated HBASE-13506:

Fix Version/s: (was: 1.2.0)
   1.2.1
   1.3.0

 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, 0.98.14, 1.0.2, 1.1.2, 1.3.0, 1.2.1


 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)


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

2015-06-15 Thread Nick Dimiduk (JIRA)

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

Nick Dimiduk updated HBASE-13506:
-
Fix Version/s: (was: 1.1.1)
   1.1.2

 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, 0.98.14, 1.0.2, 1.2.0, 1.1.2


 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)


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

2015-05-01 Thread Andrew Purtell (JIRA)

 [ 
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: 0.98.13)
   0.98.14

 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, 0.98.14, 1.0.2, 1.2.0, 1.1.1


 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)


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

2015-04-27 Thread Nick Dimiduk (JIRA)

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

Nick Dimiduk updated HBASE-13506:
-
Fix Version/s: (was: 1.1.0)
   1.1.1
   1.2.0

 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, 0.98.13, 1.0.2, 1.2.0, 1.1.1


 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)


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

2015-04-20 Thread Andrew Purtell (JIRA)

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

Andrew Purtell updated HBASE-13506:
---
Description: 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.   (was: 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 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. )

 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.1.0, 0.98.13, 1.0.2


 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)