Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90930 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95876 invoked from network); 26 Jan 2016 07:38:06 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jan 2016 07:38:06 -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.160.177 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.160.177 mail-yk0-f177.google.com Received: from [209.85.160.177] ([209.85.160.177:33151] helo=mail-yk0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B5/F1-10534-C5227A65 for ; Tue, 26 Jan 2016 02:38:05 -0500 Received: by mail-yk0-f177.google.com with SMTP id k129so191158075yke.0 for ; Mon, 25 Jan 2016 23:38:04 -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=AsVZmDoMvw6SWdJQAOYtcLpAOqh6vkYwuq3myu4UO9U=; b=XnCKysvpCkv92qvaDjkvGYm4OBgT0CAZ7AQTHAxqiFj3LYtUl3uhWr76Z4Ndw+0Xqv qmq7snc70mx9ZYa+Vgxxmt3qjWWzfaj6ZS1a8PA331V1NO8S4vVCutxIxzM4i409kbPD bL/PeGkYb2kpQRcKYkwFJV9qbt9PdtfXB47QHggNH5tpEXGGulsG7qOc5z2WqhbhY3ND anFibuB+BqDjUO5/CgblMxTqq8vNvh4Rh0sEBt9NFWDCOgfrjE/EhRUa47XcOqWnm0YL v4Ok8i13HjYQ02xONSWkm/uWTowkZUJt+8pmENfwMFVSev17yA2zYFzMPtQUBj/Ytdwd tNZA== 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:content-type; bh=AsVZmDoMvw6SWdJQAOYtcLpAOqh6vkYwuq3myu4UO9U=; b=flniT+wLDAnsg5Q9pJJiuLcFN0LQLMXM9PUxgyNOMKroEg7oWYDawRj5UHVVYrksU7 OCiI8V0wf50dcHxQeIocg+yhchhVev4o1LI0wr/sUUh6bCBurx1wmnNQdejRcr9tjaTJ QpzoGxt9YmGYG4RVJxGjdqNckz6laFbIqEh1VFsoZzi8C9uYssvf4EzWY//cGo+gTvbJ QV/YacILf4dPOOnD/VhxjuqSva3sLmfcJYZpDMOZ8JFa2saW/4z2LQsjzku7cd9Gjuns lgjp1r7yTMOwlJFAfuaYHawS3Aev2dZmVEwHSDIRQ3r+BViF6/IAb6YSnoUGFhxh48lm FwOA== X-Gm-Message-State: AG10YOTWWlRI5RW3Y7yB86tjCU2K8HXTAFiiCPEUdcqhT/OO5UCp0aRGZtX2Hflaw91Qo6zd0XS8G/TVhaJkrA== X-Received: by 10.37.42.202 with SMTP id q193mr4074553ybq.10.1453793881378; Mon, 25 Jan 2016 23:38:01 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.129.88.139 with HTTP; Mon, 25 Jan 2016 23:37:21 -0800 (PST) In-Reply-To: References: Date: Tue, 26 Jan 2016 16:37:21 +0900 X-Google-Sender-Auth: gJht3jobWwYroRFTGuPUgzwqZww Message-ID: To: "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [RFC Discussion] Precise Session Management From: yohgaki@ohgaki.net (Yasuo Ohgaki) Hi all, On Tue, Jan 26, 2016 at 4:01 PM, Yasuo Ohgaki wrote: > Since the function only allows chars used by ID, I would like to add "_" a > valid char. "_" should be very safe char. I think about possible attack/misuse scenario a little more and come up with following. "_" is wild card char of SQL's LIKE query. Although, it should be rare to use session ID string for LIKE query, one may do SELECT * FROM my_sess_table WHERE sess_id LIKE '$id'; where $id is '______________________'. This may allow to fetch all session IDs in DB. Users will likely write such query with prefixed session ID, so I don't think allowing "_" is not good idea after all. I'll keep as it is now, but if you have good option. Please let me know. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net