2017-01-04 10:53:21 +00:00
|
|
|
# MD5 and SHA-1 Deprecation
|
2017-01-04 16:16:00 -06:00
|
|
|
|
2016-03-20 16:27:54 +00:00
|
|
|
During early 2015 Homebrew started the process of deprecating _SHA1_ for package
|
|
|
|
|
integrity verification. Since then every formulae under the Homebrew organisation
|
|
|
|
|
has been moved onto _SHA256_ verification; this includes both source packages
|
|
|
|
|
and our precompiled packages (bottles).
|
|
|
|
|
|
2016-11-26 17:27:02 +00:00
|
|
|
We have stopped supporting _SHA1_ and _MD5_ entirely.
|
|
|
|
|
_MD5_ checksums were removed from core formulae in 2012 but until April 2015
|
|
|
|
|
if you tried to install a formula still using one Homebrew wouldn't actively stop you.
|
2016-03-20 16:27:54 +00:00
|
|
|
|
2016-11-26 17:27:02 +00:00
|
|
|
We removed _SHA1_ support in **November 2016**,
|
|
|
|
|
21 months after we started warning people to move away from it for verification.
|
|
|
|
|
This is enforced in the same way _MD5_ is, by blocking the installation of that
|
|
|
|
|
individual formula until the checksum is migrated.
|
2016-03-20 16:27:54 +00:00
|
|
|
|
|
|
|
|
From March 20th 2016 we've stepped up the visibility of that notification & you'll start
|
|
|
|
|
seeing deprecation warnings when installing _SHA1_-validated formula.
|
|
|
|
|
If you see these please consider reporting it to where the formula originated.
|
|
|
|
|
|
2016-11-26 17:27:02 +00:00
|
|
|
This means custom taps, local custom formulae, etc need to be migrated to use
|
|
|
|
|
_SHA256_ before you can install them.
|
