You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Wenzhe Zhou (Jira)" <ji...@apache.org> on 2020/10/02 04:14:00 UTC
[jira] [Updated] (IMPALA-10207) Replace MD5 hash with SHA-512 for
lineage graph
[ https://issues.apache.org/jira/browse/IMPALA-10207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenzhe Zhou updated IMPALA-10207:
---------------------------------
Description:
To support FIPS, we have to use FIPS-approved algorithms. We use MD5 hash algorithms for lineage graph. But MD5 is one of forbidden algorithms for FIPS. We have to replace MD5 with FIPS-approved algorithm, like SHA-512.
We might need to figure out if there are external dependencies on the hash. e.g. the lineage graph was consumed by component services, and maybe they somehow rely on the hash being consistent across versions (seems unlikely).
was:
To support FIPS, we have to use FIPS-approved algorithms. We use MD5 hash algorithms for lineage graph. But MD5 is one of forbidden algorithms. We have to replace MD5 with FIPS-approved algorithms, like SHA-512.
We might need to figure out if there are external dependencies on the hash. e.g. the lineage graph was consumed by component services, and maybe they somehow rely on the hash being consistent across versions (seems unlikely).
> Replace MD5 hash with SHA-512 for lineage graph
> -----------------------------------------------
>
> Key: IMPALA-10207
> URL: https://issues.apache.org/jira/browse/IMPALA-10207
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 4.0
> Reporter: Wenzhe Zhou
> Assignee: Wenzhe Zhou
> Priority: Major
> Labels: FIPS
>
> To support FIPS, we have to use FIPS-approved algorithms. We use MD5 hash algorithms for lineage graph. But MD5 is one of forbidden algorithms for FIPS. We have to replace MD5 with FIPS-approved algorithm, like SHA-512.
> We might need to figure out if there are external dependencies on the hash. e.g. the lineage graph was consumed by component services, and maybe they somehow rely on the hash being consistent across versions (seems unlikely).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org