Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:94443 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 5075 invoked from network); 9 Jul 2016 09:00:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Jul 2016 09:00:18 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.51 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.218.51 mail-oi0-f51.google.com Received: from [209.85.218.51] ([209.85.218.51:32851] helo=mail-oi0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0D/0A-18622-C1DB0875 for ; Sat, 09 Jul 2016 05:00:13 -0400 Received: by mail-oi0-f51.google.com with SMTP id u201so89177483oie.0 for ; Sat, 09 Jul 2016 02:00:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=S/p6QZwxu03wgdB8mLBixvdaaJ0GBHq8X13C7oS51ek=; b=pUhCR3MY0O9ShkjONw/fRgp9XmM7nqPiuLQ/QmzN2yQJF0/6M1/bUX0eFz7MKPn4b3 rs02/87FEeqQtmIUZPdcB8SJbHfti+fpR1DjAXa1OeNSQZZYXdoqwAxYBXEwo1NRWP+o 8+M+KSYaaQnm84WAzCgth2QEmDSHmV7UeEhp6lLZicGbRcF9k+gJ+vhTcFhz1FdwSf+/ sIl9bLeW7fiObvWP9iCpIhM3DZJhlh6NuRiWiqNXTQu+V7pz2xy3PBdo5oBCV4Sy4mQU XWCqI1hv61QcFgPynbVYnuWg90SyFZukgNSQondKm5Ke42dkgTCbKSGaLxDjjbKk+Gm4 cvAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=S/p6QZwxu03wgdB8mLBixvdaaJ0GBHq8X13C7oS51ek=; b=fjZQJETeuRYvEen0JSezaHX5Vf9vBkWJwNcSthLZzj1bzpELn3zV9KIFwBtZ8eGiXH wtSE52Nf8vCncUSPwd4/VmJs1RUvmmV+OIs4d41hBHwPk3zIPDS0xLYpzn0Qf+4YmuLx NtU035rG9niLAvjmBuwgudPjM2M6oV9WLv9wEOEsnu4R44qCXNqe1pSksMjbXi86a5mH x0E8p2CXw1SHxr4WlvpbkeGrFQqIEf2xBw3moBhJwtFAhK3SvRzXO/eD9PmFZpbfgehM guvCRLeqa/6XgNtKxy5SMDO2W5ZztNU+qnzajW4AtZ/I5muHgFPgbPknwBMhPiv3981C 4PIw== X-Gm-Message-State: ALyK8tIh1ix0Xu9I9sgH0w1YQYMFUNnaZQgAbuam3f3w5U5yr5wdl4UoM+AYfuwY/IvE+pHvDk7b80g1gQZgrg== MIME-Version: 1.0 X-Received: by 10.157.61.74 with SMTP id a68mr5651183otc.107.1468054804846; Sat, 09 Jul 2016 02:00:04 -0700 (PDT) Received: by 10.202.190.3 with HTTP; Sat, 9 Jul 2016 02:00:04 -0700 (PDT) Received: by 10.202.190.3 with HTTP; Sat, 9 Jul 2016 02:00:04 -0700 (PDT) In-Reply-To: References: Date: Sat, 9 Jul 2016 16:00:04 +0700 Message-ID: To: Leigh Cc: PHP internals Content-Type: multipart/alternative; boundary=001a11c0003827634d0537302536 Subject: Re: [PHP-DEV] [RFC][VOTE] RNG fixes From: pierre.php@gmail.com (Pierre Joye) --001a11c0003827634d0537302536 Content-Type: text/plain; charset=UTF-8 On Jul 9, 2016 3:49 PM, "Pierre Joye" wrote: > > > On Jul 9, 2016 3:19 PM, "Leigh" wrote: > > > > > > On Sat, 9 Jul 2016 at 08:48 Pierre Joye wrote: > >> > >> So, I voted no then as it is clear that you do not see a problem to > >> break codes without a single warning or time to adapt before. > >> > >> The other sections are fine and voted yes. > > > > > > For the part where you voted no. Still nobody has presented (publicly available) source that makes legitimate use of mt_srand (yes it's mt_srand that is "broken" here, not mt_rand) for deterministic streams of random numbers. I can only assume by this that almost nobody does. However, for those that do, they can still use the old algorithm. > > I am sorry but this PR possibly breaks BC and cases have been clearly explained how and why. Asking to show production code publically is not something that you should request. > > I can write a sample app to show you how but given the explanations many gave already.... Btw, no matter what will be the default mode, please include a clear explanation in UPGRADING with reference to the implementation being now used for mt and about what has changed. Doing so will ensure (more or less) that users know what changed or know what to do to get the previous behavior when desired. --001a11c0003827634d0537302536--