Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73276 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75676 invoked from network); 18 Mar 2014 18:56:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Mar 2014 18:56:52 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.41 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.192.41 mail-qg0-f41.google.com Received: from [209.85.192.41] ([209.85.192.41:34539] helo=mail-qg0-f41.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 72/00-10003-2F698235 for ; Tue, 18 Mar 2014 13:56:51 -0500 Received: by mail-qg0-f41.google.com with SMTP id i50so22344287qgf.0 for ; Tue, 18 Mar 2014 11:56:47 -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:content-type; bh=2RbfhZuqcz7IKwy23Y2h0ILzB8MuyMEW+y1fCI+KN3U=; b=qR8V1dlXo/WrX6BDGHMYmnZuAQXFwFZFX60RIpzZ0zJZ19BNTYRFhYDcdD7imElxmH EFbBosihuxfBUAf2B2HFKAIWKTZuzRZpDIvgEEL5jYaDeQL/9GKvGNTVwQDZrjyrQTLj vdQUTKdPliup8m8gAU6Ng3aspBaD0Eop6e6DzwIIwvtMzCYXElsN9Tas5+rodt9jnFLT Nb60b4FpA8HAwVxlbKGTbnGY6Lqvf+/neMPPhgr73w0nGbrSL1aCnqbLOf906r1GlukS mJURDNOwT5x0cDxIjMUHTe2XyVRwQRJJG08ziSx3FZm140/5OApIJ0okG8dqXyisYm/t 1NPg== MIME-Version: 1.0 X-Received: by 10.140.49.100 with SMTP id p91mr21423611qga.52.1395169007628; Tue, 18 Mar 2014 11:56:47 -0700 (PDT) Received: by 10.140.17.34 with HTTP; Tue, 18 Mar 2014 11:56:47 -0700 (PDT) Received: by 10.140.17.34 with HTTP; Tue, 18 Mar 2014 11:56:47 -0700 (PDT) In-Reply-To: References: <9E3AA302-1EC1-4497-996F-716555CAAB64@rouvenwessling.de> <4403BF54-041A-42F7-8B93-16EC3B2B0F43@rouvenwessling.de> Date: Tue, 18 Mar 2014 19:56:47 +0100 Message-ID: To: Adam Harvey Cc: Yasuo Ohgaki , =?UTF-8?Q?Rouven_We=C3=9Fling?= , PHP internals Content-Type: multipart/alternative; boundary=001a11370af819f78b04f4e6197c Subject: Re: [PHP-DEV] [VOTE] Timing attack safe string comparison function From: tyra3l@gmail.com (Ferenc Kovacs) --001a11370af819f78b04f4e6197c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2014.03.18. 17:14, "Adam Harvey" ezt =C3=ADrta: > > On 18 March 2014 04:23, Rouven We=C3=9Fling wrote: > > > > On 18.03.2014, at 02:04, Yasuo Ohgaki wrote: > > > > > On Mon, Feb 3, 2014 at 7:50 AM, Rouven We=C3=9Fling wrote: > > >> > > >> as I've received no further feedback I've opened the voting on "Timing > > >> attack safe string comparison function": > > >> > > >> - https://wiki.php.net/rfc/timing_attack > > > > > > Is there any progress? > > > > The pull request (https://github.com/php/php-src/pull/608) for that RFC is waiting to be merged, I hope someone gets to it before beta1. > > I'll look at merging it today. > > > > From benchmark result, overhead for timing safe comparison is negligible > > > with byte by byte comparison. > > > I would like to see timing safe "=3D=3D=3D" for 5.6, if it's possible= . (=3D=3D could > > > be timing safe, too) > > > > > > Is anyone working on it? > > > > I don't know if someone else is, but I am not. > > I'm not in favour of this =E2=80=94 identity doesn't imply timing safety,= and > I think we should keep operators as performant as possible. > Agree and afair it was explicitly stated as out of scope for this rfc. (sorry for not merging this sooner, thanks Adam for thaking care of this). --001a11370af819f78b04f4e6197c--