Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93182 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45081 invoked from network); 11 May 2016 01:06:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 May 2016 01:06:54 -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.192.53 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.192.53 mail-qg0-f53.google.com Received: from [209.85.192.53] ([209.85.192.53:34968] helo=mail-qg0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 29/6E-63163-DA582375 for ; Tue, 10 May 2016 21:06:53 -0400 Received: by mail-qg0-f53.google.com with SMTP id f74so16498584qge.2 for ; Tue, 10 May 2016 18:06:53 -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; bh=XQU4rb9+RQhEZwdzUGjlFcGLglUIczVoMcE2GP7+5nc=; b=nM9OUXIvH8IC4qOD2ncJk2FSTh+Uj9MZ3AO+/1c1xU4RkLwqhqd2RmoxzN+tkFqG+M uaq142/kfDi/xINJqzcktnBjTjJ8WM+EzdISRdm51+6a0GDesJvKUFsFI/Sm8mTg46of 7vEZzshI4QOavfq/Yt1ghF1XJ4kKtSWBNqMWB2ZE+HrFcJu3aMto6cBlUiGoxBVQCbMh YLvnGLy729X+cA48G/a1HY//NCHmPYhqY3uxpbN7ciPnERiZciSe76vRntXR5bvo38W3 RdoJ3meFKEL9pTAMxffKGVjE5LF+cf7UwrEdZwnWV8z7pM4uBx8EU4TDiSNfdowBuoqP UTHw== 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; bh=XQU4rb9+RQhEZwdzUGjlFcGLglUIczVoMcE2GP7+5nc=; b=jvSHFlO9tg/40Gb7ftVYIQAX0P05WGw+Q6uytkRTxQG5ZDC8bqPrQev7UcZMbrV8zQ +19sWo03rHAwYK1p/aVXAUc+DrxHMlFtEkhWWXUgLqq3yaqfL7srLzAaEQaAsYZ05CGC GPFeHUWtx05K0HiwCZgJhV+QzOLArLj0F4dape7DNGc6jvVRFrfe4q8qE82MXD56i/a1 RcimZzt6yzmJb3VzndK7MAcuNizSRmoUPDcZPJXuwZpbx/AI8yin+/7bf+pglOE7WDWF 1z38WRn7mgswuoxhCjTH7OLVvnB3X9/Ms1epiIlA7bfZ1v8fEGWXgBV1jAJZ0JPtOrBU ZKFQ== X-Gm-Message-State: AOPr4FV2T4ob4baztjxIjEu42SoQnuogZIJa9B1klM84o6XNfTjGM2vW8toxZNfgdn4lIOiiT63j8knOOfIo1g== X-Received: by 10.141.3.66 with SMTP id f63mr592869qhd.55.1462928810922; Tue, 10 May 2016 18:06:50 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.140.27.133 with HTTP; Tue, 10 May 2016 18:06:11 -0700 (PDT) In-Reply-To: References: Date: Wed, 11 May 2016 10:06:11 +0900 X-Google-Sender-Auth: 1hEVrEFGG4Ei5kMHObmvB6zD99c Message-ID: To: "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [RFC DRAFT] Automatic CSRF Protection From: yohgaki@ohgaki.net (Yasuo Ohgaki) Hi All, On Tue, May 10, 2016 at 12:24 PM, Yasuo Ohgaki wrote: > It's not nice to work on the same code (i.e. session module) for > multiple RFCs, but time is limited. > > I would like to hear from ideas/comments before I write patch for this. > https://wiki.php.net/rfc/automatic_csrf_protection > > Thank you for your comments. I've changed RFC target from "automatic" to "semi-automatic". i.e. Changed title. It is possible to set up web system that could be protected from CSRF attack fully, but it requires web server setting/simple php script to do so. If it requires web system modification anyway, it would be better make this feature more generic. Users has to write a setting for pages, but it should be good enough to secure simple applications. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net