Re: [RFC DRAFT] Automatic CSRF Protection
| From: | Yasuo Ohgaki | Date: | Tue, 10 May 2016 22:06:17 +0000 |
| Subject: | Re: [RFC DRAFT] Automatic CSRF Protection | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-93175@lists.php.net to get a copy of this message | ||
Hi,
On Wed, May 11, 2016 at 1:48 AM, Fleshgrinder <php@fleshgrinder.com> wrote:
> On 5/10/2016 5:24 AM, Yasuo Ohgaki wrote:
>> Hi all,
>>
>> 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.
>>
>> Regards,
>>
>> P.S. Precise session ID management is important, but this one is also
>> important. I'll finish and start voting 2 active session RFCs soon. I
>> may finish all of them hopefully.
>>
>
> -1 CSRF protection is a very specific need of some parts of a website
> and not something that is universally required
Did you read RFC?
It does not enable CSRF protection for all website, but only when it is enabled.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net