Home > slashdot > How Not To Design a Protocol

How Not To Design a Protocol

October 30th, 2010 10:17 admin Leave a comment Go to comments

An anonymous reader writes “Google security researcher Michael Zalewski posted a cautionary tale for software engineers: amusing historical overview of all the security problems with HTTP cookies, including an impressive collection of issues we won’t be able to fix. Pretty amazing that modern web commerce uses a mechanism so hacky that does not even have a proper specification.”

Source: How Not To Design a Protocol

Related Articles:

  1. RDS Protocol Bug Creates a Linux Kernel Hole, Now Fixed
  2. Physicists Call For Alien Messaging Protocol
  3. Physicists Call For Alien Messaging Protocol
  4. Using Hackage to Inform Language Design
  5. BBC To Create Internet Protocol TV Standard
blog comments powered by Disqus