Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54743 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96723 invoked from network); 20 Aug 2011 09:16:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Aug 2011 09:16:13 -0000 Authentication-Results: pb1.pair.com header.from=scott@macvicar.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=scott@macvicar.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain macvicar.net from 209.85.210.172 cause and error) X-PHP-List-Original-Sender: scott@macvicar.net X-Host-Fingerprint: 209.85.210.172 mail-iy0-f172.google.com Received: from [209.85.210.172] ([209.85.210.172:44958] helo=mail-iy0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 67/03-05787-C5B7F4E4 for ; Sat, 20 Aug 2011 05:16:12 -0400 Received: by iye7 with SMTP id 7so7903237iye.31 for ; Sat, 20 Aug 2011 02:16:09 -0700 (PDT) Received: by 10.231.29.93 with SMTP id p29mr790469ibc.93.1313831769426; Sat, 20 Aug 2011 02:16:09 -0700 (PDT) Received: from [172.16.1.91] ([204.28.120.216]) by mx.google.com with ESMTPS id a18sm1216140iba.3.2011.08.20.02.16.07 (version=SSLv3 cipher=OTHER); Sat, 20 Aug 2011 02:16:08 -0700 (PDT) References: <4E4EEED3.4070001@sugarcrm.com> In-Reply-To: <4E4EEED3.4070001@sugarcrm.com> Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-ID: <067502A9-EE30-45B4-8AB7-5C1C64A226C8@macvicar.net> Cc: PHP Internals X-Mailer: iPhone Mail (9A5274d) Date: Sat, 20 Aug 2011 02:16:05 -0700 To: Stas Malyshev Subject: Re: [PHP-DEV] 5.3.7pl1 From: scott@macvicar.net (Scott MacVicar) On 19 Aug 2011, at 16:16, Stas Malyshev wrote: > Hi! >=20 > Looks like 5.3.7 shipped with broken crypt() (see bug# 55439 and http://sv= n.php.net/viewvc/?view=3Drevision&revision=3D315218) - and I think it's a= serious problem since this means everybody's md5 passwords will stop workin= g - so should we make 5.3.7pl1? >=20 > And maybe not do these changes on 5.3, especially this close to the releas= e? 5.3.8 and lets not apply the coverity fixes during the final RC. S=