php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #74259 Release API shouldn't provide MD5 hashes
Submitted: 2017-03-17 07:55 UTC Modified: 2017-07-25 17:24 UTC
From: kelunik@php.net Assigned: pollita (profile)
Status: Closed Package: Website problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
 [2017-03-17 07:55 UTC] kelunik@php.net
Description:
------------
http://php.net/releases/?json&max=2000&version=7 shouldn't provide MD5 hashes for file integrity. MD5 is broken and can no longer be seen as collision-resistant.

I hereby propose to remove those hashes. Any tool that relies on the API and its MD5 hashes SHOULD break and be upgraded. We can announce it before doing the change, but we can't warn on such usage programmatically.

We already have SHA-256 there, which is fine. We should also add the PGP signatures we provide in the announcement e-mails.


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2017-03-17 13:48 UTC] security at paragonie dot com
> MD5 is broken and can no longer be seen as collision-resistant.

This is a bit of an understatement. It's trivial to create two files (one benign, one malicious) with the same MD5 hash.

> We already have SHA-256 there, which is fine. We should also add the PGP signatures we provide in the announcement e-mails.

+1
 [2017-07-25 17:24 UTC] kalle@php.net
-Status: Open +Status: Closed -Assigned To: +Assigned To: pollita
 [2017-07-25 17:24 UTC] kalle@php.net
Fixed by Sara
 
PHP Copyright © 2001-2019 The PHP Group
All rights reserved.
Last updated: Sun Dec 15 20:01:28 2019 UTC