News for hackers. Stuff that matters.
Re:HTTP/2.0 — Bad protocol, bad politics by stingraycharles on Wednesday January 07, 2015 @09:31AM (#8850634)
For what it's worth, the cookie law in the EU is far more general than cookies, and had a totally different origin. Originally, the law was to require explicit consent when installing something on an electronic device, to combat malware. However, some clever politicians later realized that setting a cookie also "installs" something on an electronic device, and thus the law further known as the cookie law was passed.

If a webserver were to set some secure session identifier, the same laws still apply -- just as installing software without explicit consent is covered by the same law.

Re:HTTP/2.0 — Bad protocol, bad politics by boracay on Wednesday January 07, 2015 @09:39AM (#8850681)
Not if you are using the session identifier for it's intended purpose, see the exceptions at: http://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm#se...
Re:HTTP/2.0 — Bad protocol, bad politics by stingraycharles on Wednesday January 07, 2015 @09:45AM (#8850710)
We all know how broad "intended usage" can be defined. Google has a cookie that is required for logging in into gmail (clearly intended usage), but is reusing that exact same cookie for tracking purposes.

Until there is actual legal precedence after people sueing businesses abusing these abilities, I have no idea how to interpret these laws other than "they are very broad and vague".

Re:HTTP/2.0 — Bad protocol, bad politics by boracay on Wednesday January 07, 2015 @10:00AM (#8850781)
I don't think the laws are vague so much as how we use cookies today. With different mechanisms for different purposes it would (could) be much more transparent to the end users how things work. It would be more like the "save password" feature in various browsers. Of course since all the major browsers vendors also make money from ads this isn't really in their interest.