News for hackers. Stuff that matters.
Re:This is why sites choose to stay vulnerable to Firesheep by notphilatall on Sunday November 07, 2010 @09:16PM (#1881111)
How about: Give every user a monotonically incrementing value that's initialized at the start of the session using HTTPS. For every request, the client will provide the next value in the expected sequence. Listeners won't have the secret key that was exchanged during the HTTPS authentication, and can't issue requests on the legitimate client's behalf.

Forcing the requests to be serial sucks, but if you only do it for privileged actions (as opposed to public page GETs) it should be manageable.

Re:This is why sites choose to stay vulnerable to Firesheep by zbanks on Sunday November 07, 2010 @09:24PM (#1881127)
Still vernerable to MITM attacks, since an attacker could intercept a legitimate respo se for safe.js, but then send the user a completely different file. You need to sign the entire file. Now you're incredibly close to having SSL.