Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71988 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60871 invoked from network); 2 Feb 2014 10:25:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Feb 2014 10:25:55 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.107 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.107 smtp107.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.107] ([108.166.43.107:49323] helo=smtp107.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 68/87-30967-13D1EE25 for ; Sun, 02 Feb 2014 05:25:54 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 1926A980EF; Sun, 2 Feb 2014 05:25:51 -0500 (EST) X-Virus-Scanned: OK Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id BBB75980EE; Sun, 2 Feb 2014 05:25:50 -0500 (EST) Message-ID: <52EE1D2E.8060309@sugarcrm.com> Date: Sun, 02 Feb 2014 02:25:50 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Yasuo Ohgaki CC: "internals@lists.php.net" References: <52ED7AC8.6080703@sugarcrm.com> <52EDF03C.5080201@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Secure Session Module Options by Default From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > It could have signature like > > string session_id(string $prefix_or_id [, bool $use_prefix]); I'm not sure what prefix has to do with this RFC. Didn't we talk about secure setting? Where the prefix came from and why we need the prefix at all? > We have to decide what we will do about use_strict_mode behavior. > It may be easier automatically set use_strict_mode=FALSE. I'm not sure I understand. So if strict mode is on, when I do session_id('foo') and session with ID foo does not exist, what would happen? Would session_start() create it or would it generate new ID, effectively ignoring my session_id command silently? > I would like to expand uniqid() or create new function that returns > secure random string, so session_create_id() is not mandatory. Don't we have such function already? http://us1.php.net/manual/en/function.mcrypt-create-iv.php -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227