Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71954 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95447 invoked from network); 2 Feb 2014 00:00:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Feb 2014 00:00:44 -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.217.179 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.217.179 mail-lb0-f179.google.com Received: from [209.85.217.179] ([209.85.217.179:58109] helo=mail-lb0-f179.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AB/5B-30967-AAA8DE25 for ; Sat, 01 Feb 2014 19:00:43 -0500 Received: by mail-lb0-f179.google.com with SMTP id l4so4331833lbv.24 for ; Sat, 01 Feb 2014 16:00:40 -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:cc:content-type; bh=cwKQm6LWCAuOScoNvZgL7g7rGh+X6ZesAH32LgrSSZw=; b=NXwsYFrCkxTuN/G78P/s/CPqIUxYvhvQFmfvq2FjjY5Gu8MKN2nkDWEkZoI6weVHpV IE6nXFAigLzcbfschyvZ0H9SmXnXke9NVGjy9p531AcGsFkOahNvGSRv65V9QN/G3X31 2DN1zbU4rnt7bsQA+cioRVsyQv+WBLCrmLQ5b5imu6ihcSW8UMTRzds8uQx0GC4VLYkd Eg3PfSQwBTSVihZeCvOpv1PDJGe445D6D4ymcGZV0bKttxe7tJIJhxeNl0qxNKPfqByw jL4V7L4E7mMCeTwGdPdCVDwtfkisFtSxuPjBEAn/8olhlAVgxemUUWo/fPYu2UEmd/wY jLdg== X-Received: by 10.112.137.65 with SMTP id qg1mr3889121lbb.7.1391299240094; Sat, 01 Feb 2014 16:00:40 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.199.37 with HTTP; Sat, 1 Feb 2014 15:59:59 -0800 (PST) In-Reply-To: <52ED7AC8.6080703@sugarcrm.com> References: <52ED7AC8.6080703@sugarcrm.com> Date: Sun, 2 Feb 2014 08:59:59 +0900 X-Google-Sender-Auth: xGamrmyycZ4WHo8-xSFjxdmpi-o Message-ID: To: Stas Malyshev Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=089e0116047efb741804f1611824 Subject: Re: [PHP-DEV] [RFC] Secure Session Module Options by Default From: yohgaki@ohgaki.net (Yasuo Ohgaki) --089e0116047efb741804f1611824 Content-Type: text/plain; charset=UTF-8 Hi Stas, On Sun, Feb 2, 2014 at 7:52 AM, Stas Malyshev wrote: > > Secure Session Module Options by Default > > https://wiki.php.net/rfc/secure-session-options-by-default > > use_strict_mode - I'm not sure I understand what "Change session_id() to > allow any id regardless of this mode." means. Since there's no patch > attached, could you explain the change in more detail? When use_strice_mode=On, session_id($some_new_id); will generate random session ID, since there is no initialized session data for it. (This is what use_strict_mode=On supposed to do) However, user may set their own session ID which contains some data in session ID name via session_create_id([string $prefix]). e.g. time created/regenerated/etc. To set user defined session ID, user has to do ini_set('session.use_strict_mode', FALSE); session_id(session_create_id('SOME-USEFUL-PREFIX')); With this change, user could do session_id(session_create_id('SOME-USEFUL-PREFIX')); regardless of INI settings. session_id() is changed to modify 'session.use_strict_mode' INI to off internally. This change is not mandatory as user may change INI by themselves. It's for convenience. I don't mind at all withdrawing this change from the RFC. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --089e0116047efb741804f1611824--