Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69391 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47919 invoked from network); 27 Sep 2013 11:00:48 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Sep 2013 11:00:48 -0000 Authentication-Results: pb1.pair.com smtp.mail=peter.e.lind@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=peter.e.lind@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.177 as permitted sender) X-PHP-List-Original-Sender: peter.e.lind@gmail.com X-Host-Fingerprint: 74.125.82.177 mail-we0-f177.google.com Received: from [74.125.82.177] ([74.125.82.177:64921] helo=mail-we0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0D/21-42235-E5565425 for ; Fri, 27 Sep 2013 07:00:48 -0400 Received: by mail-we0-f177.google.com with SMTP id t60so2449836wes.36 for ; Fri, 27 Sep 2013 04:00:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=jTcLJtV7Pf+3Hpq7Pv72oH59zk5cFi7TpkOEyU6SXc8=; b=FSNisYPEvgOyWw00OWCPdCgVf/2R6l14oafa8woYj4unhKJe0JBxsOUC2fe+l3Lf9T usRSqNFFa60s6OytxJHgv7IvynDXDsmE+t9D8akrBYSPmsqrYIcCmvsy5ytjReY1VDQi 7ou1oCLo+mYBQhWPYP8wN2pe36NR6RIshbpMRNPsFB1H2sZ+Ct6hOUH7WzQ+Ob0sgR9P aNSocf5sS/EH14Qoteb5OnM6k+qkCX59U2lAUCKQpBrquYfnnDI3efC4NtdhaApvazk8 KSpir2P24QQ6m+u0ssSneuH7eRN7jqjX1G90C91xq6hQUTIeTGeY7Y67lAXM+QgHzdvG 7ovg== X-Received: by 10.194.119.8 with SMTP id kq8mr1240763wjb.45.1380279644231; Fri, 27 Sep 2013 04:00:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.198.134 with HTTP; Fri, 27 Sep 2013 04:00:24 -0700 (PDT) In-Reply-To: References: Date: Fri, 27 Sep 2013 13:00:24 +0200 Message-ID: To: Leigh Cc: Tjerk Meesters , PHP Internals , Yasuo Ohgaki Content-Type: multipart/alternative; boundary=089e011777fbe2a0a804e75b6539 Subject: Re: [PHP-DEV] Regenerating session ID automatically when IP address has changed From: peter.e.lind@gmail.com (Peter Lind) --089e011777fbe2a0a804e75b6539 Content-Type: text/plain; charset=UTF-8 On 27 September 2013 12:54, Leigh wrote: > On 27 September 2013 11:39, Peter Lind wrote: > > On 27 September 2013 12:12, Leigh wrote: > >> > >> So on a successful session hijack (correct SID, new IP) the attacker > >> gets a new SID and keeps the valid session while the legitimate user > >> gets kicked out. > >> > >> Not seeing how that improves things at all. > > > > In your scenario, user gets booted and thus knows somethings wrong. Much > > better than the attacker hijacking the session without the user knowing > > anything at all. > > > > Regards > > Peter > > And what is done to invalidate the session now gained by the attacker? > Since this is a proposal to handle such things internally. > > And what is done when the user thinks everything is fine and dandy? My point was that the scenario you created did not pose a problem - if anything it would be a benefit (as you actually *can* detect some problems now). Do you really think random user X will think something is wrong beyond > the site they were using just kicking them out for no reason? So now > what do they do now? Log in again? The attacker still has the > previously valid session, so nothing is gained. > > That's for the userland code to decide. > This is exactly why this kind of logic belongs as user code. We're > starting to define rules for a system that should be agnostic to how > it is being used. > I would agree. I was just pointing out that your example was not in fact much of an argument against the proposal. Regards Peter -- WWW: plphp.dk / plind.dk CV: careers.stackoverflow.com/peterlind LinkedIn: plind Twitter: kafe15 --089e011777fbe2a0a804e75b6539--