Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93199 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81515 invoked from network); 11 May 2016 05:20:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 May 2016 05:20:03 -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.220.195 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.220.195 mail-qk0-f195.google.com Received: from [209.85.220.195] ([209.85.220.195:34782] helo=mail-qk0-f195.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 54/B3-64493-201C2375 for ; Wed, 11 May 2016 01:20:02 -0400 Received: by mail-qk0-f195.google.com with SMTP id i7so2352188qkd.1 for ; Tue, 10 May 2016 22:20:02 -0700 (PDT) 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:cc; bh=YDSNw3lEA62nBXlORm7F1VZoPPzB8CbJlro/uB1TB7g=; b=S1lHAdZeH7QzqXKg3G3zOD7ILnCMPb4DwBpaLLHowTqEygbptTr7vSyNKnZRECZHhX C0BgMx2kZvY+OYi0SwY78ag5nZ5f5DmUZ69ABYybETU5gTxbq2iUwTUFUk51PFJXq3Go nKq2AIBQTJ7c1jTHHH+OGsZQg+Y3v4xbm+BYJYqa8nt/NarehG6N634EJX54DhKaBk0L l7Dg0I+mFt7RftdVNpW68cGmUcFNz+KM2IQXiy0rfaRdSt8tdei4TnFUr8sfI+SuduaV TV5NMc48FcTpIINqpCJgcUa1SLFMWqrwMDSby37QikPr2VwjVBODmKFxf1k5ieiTn47e Wt7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=YDSNw3lEA62nBXlORm7F1VZoPPzB8CbJlro/uB1TB7g=; b=fTCYhTJBt9paZMwdcZTs2UaUJ8J751Dk9EcAZDtKExGCQza0OPtf4G/bc8hVuEe9yP mSlm0WM07vTosUnb2fPTAOJsRGq9DErd8NMSxA3mUgWTMAJNH3JJDj4v2nRuMJM9DE0k F+laoDPUuQBbgcUnZR3FK1H1Ss4A7O1JMvPv0Gh9RdQ1vPVxiyyIUShs3yebTSJmCnY/ 6KnjJC3hopQ6/JVMZ065c1p1yoe3a5nImCXWf3w64odCWYyFbj/lCN181RjuH8j2cUXa QzAvl4Ofg9eg/OeFWGc4v6G/lXAP1lnsmdHj0hrEDKNqsnB3m6a0IavrBcKgqb7Be/tB nifg== X-Gm-Message-State: AOPr4FVWgOeexnaQxQj7SrqCQS8U1wUcm6PFUwFnegglJrPT4PyvfhEHHdlqXPtB1ao2Iksa2BsvCBVusMddMg== X-Received: by 10.55.80.136 with SMTP id e130mr1464349qkb.28.1462943999100; Tue, 10 May 2016 22:19:59 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.140.27.133 with HTTP; Tue, 10 May 2016 22:19:19 -0700 (PDT) In-Reply-To: References: Date: Wed, 11 May 2016 14:19:19 +0900 X-Google-Sender-Auth: yqj7jz0BpYlL5-LvhHqnvX152WQ Message-ID: To: Pierre Joye Cc: PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC DRAFT] Automatic CSRF Protection From: yohgaki@ohgaki.net (Yasuo Ohgaki) Hi Pierre, On Wed, May 11, 2016 at 1:12 PM, Pierre Joye wrote: > The current session code and designs is old, very old. It does not match > today ways to do things. Every time we fix it, I see a band aid fix. Let's rewrite session module someday. In the meantime, I would like to add features to make session management like TCP. We don't have to care about authenticity (CSRF) with TLS/TCP, but web developers must care with TLS/HTTP :( Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net