[
https://issues.apache.org/jira/browse/HDFS-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444615#comment-13444615
]
Andy Isaacson commented on HDFS-3859:
-------------------------------------
Bunch of touchy feely reasons:
# mere presence of MD5 in the code is a red flag to auditors. We then have to
spend time arguing with people over whether it's a security issue.
# think of broken crypto protocols as similar to asbestos. It's perfectly
possible to create safe products that include asbestos (and in some cases
they're much cheaper and better performing than a non-asbestos-containing
substitute). But nobody does this because the stigma is too great, and too many
times a vendor's statement "my product is safe" turns out to be false, so it's
easier to just move on.
# building new code that uses old broken primitives just extends the time
before we can delete the implementations of the old broken primitives. Better
to move forward when the opportunity exists.
> QJM: implement md5sum verification
> ----------------------------------
>
> Key: HDFS-3859
> URL: https://issues.apache.org/jira/browse/HDFS-3859
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Affects Versions: QuorumJournalManager (HDFS-3077)
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hdfs-3859-sha1.txt
>
>
> When the QJM passes journal segments between nodes, it should use an md5sum
> field to make sure the data doesn't get corrupted during transit. This also
> serves as an extra safe-guard to make sure that the data is consistent across
> all nodes when finalizing a segment.
--
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
