Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96417 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89136 invoked from network); 18 Oct 2016 09:43:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Oct 2016 09:43:04 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:33141] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 63/57-40890-5AEE5085 for ; Tue, 18 Oct 2016 05:43:03 -0400 Received: (qmail 3729 invoked by uid 89); 18 Oct 2016 09:42:59 -0000 Received: by simscan 1.3.1 ppid: 3723, pid: 3726, t: 0.0407s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.7?) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 18 Oct 2016 09:42:59 -0000 To: internals@lists.php.net References: Message-ID: <52a34722-ccd4-b875-2c1b-f704117ef708@lsces.co.uk> Date: Tue, 18 Oct 2016 10:42:58 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: [RFC][DISCUSSION] Improve uniqid() uniqueness From: lester@lsces.co.uk (Lester Caine) On 18/10/16 08:35, Yasuo Ohgaki wrote: >> Sure, but it did happen that shared hosts block it, noticed during >> > random_compat adoption. >> > >> > You claimed there isn't any BC break. > The line should be > > "There is no BC for usable systems" > > Any file permission could disturb PHP script execution, couldn't it? > > I think it's nothing special for /dev/urandom. User should set up system > correctly to use PHP. Then there is no BC at all. 'Suppliers' should perhaps be helped to configure their systems so the users can use things, but things like /dev/urandom may need some additional notes to help identify problems when frameworks like owncloud start throwing errors. As Niklas says it's shared environments where this one may bite. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk