Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71165
Return-Path: <yohgaki@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 61526 invoked from network); 16 Jan 2014 00:13:29 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 16 Jan 2014 00:13:29 -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.217.172 as permitted sender)
X-PHP-List-Original-Sender: yohgaki@gmail.com
X-Host-Fingerprint: 209.85.217.172 mail-lb0-f172.google.com  
Received: from [209.85.217.172] ([209.85.217.172:63999] helo=mail-lb0-f172.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 69/52-48719-82427D25 for <internals@lists.php.net>; Wed, 15 Jan 2014 19:13:29 -0500
Received: by mail-lb0-f172.google.com with SMTP id c11so1366606lbj.31
        for <internals@lists.php.net>; Wed, 15 Jan 2014 16:13:24 -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=4HPhz763RbQL8wDYIGJrllY7uaKvDotuSR6E8DCpvzs=;
        b=vXG/NuOiQKKPA+fJ4h0a1FL4pxH6PZegT/aA2/lG+qNVJzZ/BWVMpJGCimbSKW8y09
         Rh7ZcNn1vyxBqp72uRZw6LYJJ2vCR5LGc0Tl0ddUPdmDN5pd5vO1vRHklOgk1SWsgBvt
         QoY2atBx+8Mc7k01EZtZY9oAj3LyHhoM3N0g0EtZZ3T2lmooHlROM/UAlA8S8DOx4YDX
         0qCUm/mQgF8cfhsfaRtaK6nD1dXRClcLDnfoaebXjIRE5gsPOdpqR5uy88foiLWb6ptO
         +eWlqUy1ZIn9HDFACrydErjtkPnvcxpSI5T89KEogC4BDMEvJn5NyfdjdL14jT0IwVqS
         IzEA==
X-Received: by 10.112.136.36 with SMTP id px4mr230667lbb.46.1389831204719;
 Wed, 15 Jan 2014 16:13:24 -0800 (PST)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
Received: by 10.112.6.68 with HTTP; Wed, 15 Jan 2014 16:12:44 -0800 (PST)
In-Reply-To: <CAGa2bXauxj6Sca8qYk2cxQ=TeG4bjWgcv-Aqy3cJe35ap72Yfw@mail.gmail.com>
References: <CAGa2bXauxj6Sca8qYk2cxQ=TeG4bjWgcv-Aqy3cJe35ap72Yfw@mail.gmail.com>
Date: Thu, 16 Jan 2014 09:12:44 +0900
X-Google-Sender-Auth: hinXjsHxrBIz82IMVdv41kJ8Nks
Message-ID: <CAGa2bXakKhtag+HsQhAYuYfVof=13W=zmHhCTUNPRd1+t_mdSA@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0118311041523a04f00b4bf3
Subject: Re: [RFC] Multibyte char handling
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--089e0118311041523a04f00b4bf3
Content-Type: text/plain; charset=UTF-8

Hi all,

On Thu, Jan 16, 2014 at 8:50 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> 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 copied line from "Array Of" RFC and URL was wrong.
Correct URL is

https://wiki.php.net/rfc/multibyte_char_handling

Sorry for the confusion.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--089e0118311041523a04f00b4bf3--