Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71421 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91451 invoked from network); 23 Jan 2014 04:40:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jan 2014 04:40:27 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.46 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.46 mail-la0-f46.google.com Received: from [209.85.215.46] ([209.85.215.46:53592] helo=mail-la0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 82/70-23060-A3D90E25 for ; Wed, 22 Jan 2014 23:40:26 -0500 Received: by mail-la0-f46.google.com with SMTP id b8so1062513lan.33 for ; Wed, 22 Jan 2014 20:40:23 -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=f3lpX7zKBVw5h2CXh55LHUYRo+hgevDP5iOVSaIcBsA=; b=tP50m0muFiUVlPtsvypDghfAswGATXkqVFSD16x5mPtT9+t3GuQWtiFCeHcf2Fxx7C yJZrp0Q0MT9Yo5sL2gRRaeCT4/Xc8ZKYWewBRKTfr25e6DyWkfLUbPncKha+6jq5Vh4L LFDq5jf3OylxqD5RGlf4NAOCJ9skv0Nxbd+BO2ndKT/QZnkehTjvqY54ho9Hvz9WNV5o sXmbcgLr+NHAUHOSYiFG9y+4LiGFXAWSQNYoiwyAwpOymvu7vwO5s7v9pXbyI9QKTotO TxERtSVrVhypdGajSOLruBhOv4YmdvM4kYe+CKhuRJTJyroBw1NeVm9YhltsIG0Mn75u Cxqw== X-Received: by 10.112.64.67 with SMTP id m3mr3403580lbs.11.1390452022928; Wed, 22 Jan 2014 20:40:22 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.132.134 with HTTP; Wed, 22 Jan 2014 20:39:42 -0800 (PST) In-Reply-To: References: Date: Thu, 23 Jan 2014 13:39:42 +0900 X-Google-Sender-Auth: oMQpIMTVpeGNsuWIuPK8TWNsT4k Message-ID: To: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11c3f924e7693e04f09bd6d3 Subject: Re: [RFC] Multibyte char handling From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c3f924e7693e04f09bd6d3 Content-Type: text/plain; charset=UTF-8 Hi all, On Thu, Jan 16, 2014 at 8:50 AM, Yasuo Ohgaki wrote: > addslashes() could be vulnerable via char encoding based attacks. > It is needed to decide what counter measure we adopt. > This is RFC for this issue. > > https://wiki.php.net/multibyte_char_handling > > Please comment. > Thank you. > I've revised the RFC a little and integrated with following RFC. Alternative implementation of mbstring using ICU https://wiki.php.net/rfc/altmbstring RFC is changed to include mbstring-ng as a default compiled module. It would be better for license wise. IMHO. If there is no additional comment, I would like to start vote. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c3f924e7693e04f09bd6d3--