Re:How To Protect Your Login Information From Firesheep
by whakojacko on Monday October 25, 2010 @03:40PM
(#1831272)
If it were possible to pass the cookie on an encrypted channel but the content of the web page unencrypted this would match most people's idea of how it works. Unfortunately that's not the case.
Has there even been any attempt to standardize something like this? This problem certainly isn't a new one, so I would have guessed this had been looked into before
Re:How To Protect Your Login Information From Firesheep
by pornel on Tuesday October 26, 2010 @07:36AM
(#1833775)
> Has there even been any attempt to standardize something like this?
Yes. HTTP Digest authentication is an "encrypted cookie".
The problem is that it only protects against passive sniffing. Attacker able to inject packets can bypass it (e.g. replace Digest with Basic auth.)
For most people there is a huge gap between "can read everything I write" and "can gain full control/impersonate me". On the technology side, these two things are unfortunately coupled. It is way more than a privacy risk.
If it were possible to pass the cookie on an encrypted channel but the content of the web page unencrypted this would match most people's idea of how it works. Unfortunately that's not the case.