Regrettably, there are many places in chromium where we use and need to
continue using md5 hashes for compatibility with existing file formats
or protocols. At the moment implementations of these use base/hash/md5,
but the //base owners would very much like to kick that code out of
//base. Therefore, this change adds a new md5 implementation as
//crypto/obsolete/md5 and adds a large deprecation warning to the
existing //base implementation. Using crypto/obsolete/md5 requires
review by a CRYPTO_OWNERS member, and this is enforced using visibility
rules.
Bug: 406729261
Change-Id: I426dbd46aec358ef300d5f5a5bbb5adc881bc78b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6432267
Reviewed-by: Bob Beck <bbe@chromium.org>
Commit-Queue: Elly FJ <ellyjones@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1442511}
35fe484d1d