News for hackers. Stuff that matters.
Re:RFC 6896 – Secure Cookie Sessions for HTTP by kpcyrd on Thursday December 20, 2018 @04:11PM (#18729155)
It seems this has all disadvantages of jwt-style sessions, plus a BREACH-style vulnerability in the crypto due to compression if `plain-text-cookie-value` contains data an attacker can taint.
Re:RFC 6896 – Secure Cookie Sessions for HTTP by tptacek on Thursday December 20, 2018 @06:56PM (#18730349)
Yeah, I'm pretty confused by this being on the front page.
Re:RFC 6896 – Secure Cookie Sessions for HTTP by ryacko on Thursday December 20, 2018 @06:59PM (#18730364)
Worse: “SCS doesn't address replay of old cookie values.”
Re:RFC 6896 – Secure Cookie Sessions for HTTP by jamieson-becker on Thursday December 20, 2018 @03:52PM (#18729010)
@moderators should probably be marked [2013]
Re:RFC 6896 – Secure Cookie Sessions for HTTP by chrismorgan on Thursday December 20, 2018 @04:43PM (#18729413)
A better title:

RFC 6896 - SCS: KoanLogic's Secure Cookie Sessions for HTTP [2013]

Re:RFC 6896 – Secure Cookie Sessions for HTTP by jedisct1 on Friday December 21, 2018 @10:00AM (#18733651)
A better better title: RFC 6896 - SCS: KoanLogic's Insecure Cookie Sessions for HTTP [2013]
Re:RFC 6896 – Secure Cookie Sessions for HTTP by kerng on Friday December 21, 2018 @11:04AM (#18734131)
This doesn't seem to protect from Pass the Cookie attacks.

Edit - it's a common red teaming tactic: https://wunderwuzzi23.github.io/blog/passthecookie.html

Re:RFC 6896 – Secure Cookie Sessions for HTTP by 0xfffff on Friday December 21, 2018 @11:14AM (#18734218)
Correct, it doesn't. If you grab that cookie and then pass the cookie from somewhere else it will work.

Section 7.2.3 talks about cookie theft.

Re:RFC 6896 – Secure Cookie Sessions for HTTP by kerng on Friday December 21, 2018 @11:22AM (#18734287)
Yeah, as others have pointed out this RFC is from 2013 - so a bit dated.