Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72508 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 9654 invoked from network); 12 Feb 2014 10:07:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Feb 2014 10:07:12 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.44 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.44 mail-la0-f44.google.com Received: from [209.85.215.44] ([209.85.215.44:47774] helo=mail-la0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 81/81-00747-CC74BF25 for ; Wed, 12 Feb 2014 05:07:10 -0500 Received: by mail-la0-f44.google.com with SMTP id hr13so6993485lab.3 for ; Wed, 12 Feb 2014 02:07:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=XXbkF0ckO3SZ9hSa8M28tK91PiMAD4PGoNaTG1ipQ8k=; b=dQnnhEQA2FQX3xLLPy+xVNn1BZqAFT8O/lSNeCSroz1fKIijjBAQgSBP9UBdsNtKPN GT8QdxwEogZeRGRqCKWgZntLAVDIAV6zy9qHvppVusBHIWQEwF0Jsu8zUSU2SGx4Dbx8 NyOfz4tkjdcuJKVtk+Mrg7PzF+C/U3rH29VT2Rff4aubgRfAXYm6FscpOXYi5u4EhG2S sHJyKpwfvubA9EsB2ISpDsqB43qLX1er1GgJ3LURA2P2lpdmth0qOHJJew1uBvRiOOUj D/lcLAzAYo7vNX7lG6P9bOi5BzIN6yY94vH/+8suQ72EK0TIALBy+SuIPHNTvpB5MFw9 4uLw== X-Received: by 10.152.120.37 with SMTP id kz5mr27439820lab.30.1392199625073; Wed, 12 Feb 2014 02:07:05 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.199.37 with HTTP; Wed, 12 Feb 2014 02:06:24 -0800 (PST) In-Reply-To: References: Date: Wed, 12 Feb 2014 19:06:24 +0900 X-Google-Sender-Auth: 9KPNJcuKVb6t81o81I42gVl32RM Message-ID: To: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=089e012281481bea2f04f232bc0a Subject: Re: [VOTE] Multbye char handling - Remove vulnerability related to multibyte short and long term From: yohgaki@ohgaki.net (Yasuo Ohgaki) --089e012281481bea2f04f232bc0a Content-Type: text/plain; charset=UTF-8 Hi all, On Mon, Feb 10, 2014 at 12:56 PM, Yasuo Ohgaki wrote: > Long term: Alternative implementation of mbstring using ICU > https://wiki.php.net/rfc/altmbstring > We need multibyte feature as default. However, current mbstring has > license issues. Resolve license issues by alternative mbstring in the > future. Introduce mbstring-ng as EXPERIMENTAL module for further > development, testing, feedback from users. > All of voters other than me voted no, so far. I would like hear the reason. We can make future PHP handles all encoding. How many of you prefer this options? To be honest, I'm +1 for this. However, it seems there are many people against it. e.g. Encoding parameter/property seems to have many objections. Since this is technical discussion, objection without reason is not constructive. Thank you for sharing your opinions! Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --089e012281481bea2f04f232bc0a--