6a5c928539
Prior to this patch hbase always used the MD5 hash algorithm to store a hash for encryption keys. This hash is needed to verify the secret key of the subject. (e.g. making sure that the same secrey key is used during encrypted HFile read and write). The MD5 algorithm is considered weak, and can not be used in some (e.g. FIPS compliant) clusters. In this patch we: - add a config parameter to globally enable/disable column family encryption (def enabled) - introduce a backward compatible way of specifying the hash algorithm. This enable us to use newer and more secure hash algorithms like SHA-384 or SHA-512 (which are FIPS compliant). - add a config parameter to fail if an hfile is encountered that uses a different hash algorithm than the one currently configured to ease validation after migrating key hash algorithms (def disabled) Closes #2539 Signed-off-by: Sean Busbey <busbey@apache.org> Signed-off-by: Esteban Gutierrez <esteban@apache.org> |
||
|---|---|---|
| .. | ||
| src | ||
| pom.xml | ||