Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99375 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 25204 invoked from network); 5 Jun 2017 18:56:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jun 2017 18:56:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=kalle.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=kalle.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.41 as permitted sender) X-PHP-List-Original-Sender: kalle.php@gmail.com X-Host-Fingerprint: 209.85.214.41 mail-it0-f41.google.com Received: from [209.85.214.41] ([209.85.214.41:35384] helo=mail-it0-f41.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E4/75-27119-D59A5395 for ; Mon, 05 Jun 2017 14:56:29 -0400 Received: by mail-it0-f41.google.com with SMTP id m62so71264054itc.0 for ; Mon, 05 Jun 2017 11:56:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=5kmPvPdWszk56NJXzSNZSkLNie9qWk2guJu9lbwIS08=; b=KyoOoN7lv9m8htqZ8SpUCxDWEPoxO/hWXQfc6pHCoUXx9zSuuCMc7gRY5RtXXFhG9/ CG77vN5hNNa01IzkLCvY6zJ0HC0xOlIUIkHLeUkDtqfs7c0aPn1i+XBjt7kC1rBecU+m Uu4n2RZ9iKzbWm0AKL7oqRHq6roNkRnBtKCjMlJqNw2TOED62vLSYg682jph6Si5LpFK I6QKIPGOOLUBI9ytOHHrMIeoHF3JruVkG3tSkdSHiLHGgvsBEWHVmhrXAPBMgrx1e/LI r5DGK5FwKKIfxz7HGrnFDp9nzWp1qwoMhMZ5fdNWN4FuYVklSxw44x0ISOcIbzSie8Xr 5nsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=5kmPvPdWszk56NJXzSNZSkLNie9qWk2guJu9lbwIS08=; b=enlrKILK6Cr/exAsPmS9uXQo1UHPK5Ex/BUiAeZSw7UkdxsPGZtWWKU4fNfPO7fSnE LJkzlliXXjzVZo2IqgHgMJOwj9tjtOGrIwoE1BZtODoSPppTgQk6ssQEfz6t0a8QaA7C nekf06iZAFFEG5GovtciyNcv3O/9n1Fn87UcUgYSLl+0N7ljkKvM9YCqX6JASWgwUCWJ jJZS/n0Sc1rgFIUAIDxT97dTgSz/3nA2GF2HyuLsw20DOjAPY/OCqQnGs9DnbvyiwcXs QpnhjGnDA3enetTp8etr27tGw+vvZKw0UhmeLUNpe3UWvlCswslwCP/Ekoa/otc8hhc0 kxmg== X-Gm-Message-State: AODbwcBrbgCgyZbauGZrOM9qMp+due3Wmbt+K5xFqh0lukDahf48uLLT Xt9WsXQ5UKb/zEr9fr6yFpZU6yBF8Q== X-Received: by 10.107.59.67 with SMTP id i64mr20866123ioa.43.1496688985906; Mon, 05 Jun 2017 11:56:25 -0700 (PDT) MIME-Version: 1.0 Sender: kalle.php@gmail.com Received: by 10.107.18.132 with HTTP; Mon, 5 Jun 2017 11:56:25 -0700 (PDT) In-Reply-To: References: Date: Mon, 5 Jun 2017 20:56:25 +0200 X-Google-Sender-Auth: eXsGcfm3iyRDcsXrcWz1mhhDL40 Message-ID: To: Sara Golemon Cc: Niklas Keller , PHP internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] Re: [RFC][Release Process] Deprecate/Remove MD5 checksums From: kalle@php.net (Kalle Sommer Nielsen) > That's not a terrible idea. I'll script something up to download, > verify gpg if it's available (verify existing m5 if it's not), and > generate a sha256 from it resulting in a diff to > web-php/include/releases.inc . Can do that irrespective of whether or > not we stop adding md5s. We also got MD5 checksums over at the QA site, but I recently (like a year ago) added SHA-256 checksums there, so it should be really easy to get rid of the MD5s -- regards, Kalle Sommer Nielsen kalle@php.net