Transport Layer Security Channel ID: Difference between revisions

Revision as of 08:26, 21 August 2016

Revision as of 07:24, 22 August 2016

Line 7:

It can also protect users from the related ___domain cookie attack.<ref>[http://security.stackexchange.com/a/12419/396 "Related Domain Cookie Attack"]{{unreliable source?|date=September 2013}}</ref><ref>[https://stackoverflow.com/q/9636857/328397 additional info is available here]{{unreliable source?|date=September 2013}}</ref>

[[Token Binding]] is an evolution of the TLS Channel ID feature,<ref>{{cite web|url=https://www.google.com/chrome/browser/privacy/whitepaper.html#tls|title=Google Chrome Privacy Whitepaper|publisher=Google Inc.}}</ref> and the IETF draft has authors from Microsoft and Google on it.<ref>{{cite web|url=https://tools.ietf.org/html/draft-ietf-tokbind-protocol-04|title=The Token Binding Protocol Version 1.0|author=A. Popov, Ed., M. Nystroem, Microsoft, D. Balfanz, A. Langley, Google|date=2016-01-08}}</ref>

[[Token Binding]] is an evolution of the TLS Channel ID feature

,<ref>{{cite web|url=https://www.google.com/chrome/browser/privacy/whitepaper.html#tls|title=Google Chrome Privacy Whitepaper|publisher=Google Inc.}}</ref> and the IETF draft has authors from Microsoft and Google on it.<ref>{{cite web|url=https://tools.ietf.org/html/draft-ietf-tokbind-protocol-04|title=The Token Binding Protocol Version 1.0|author=A. Popov, Ed., M. Nystroem, Microsoft, D. Balfanz, A. Langley, Google|date=2016-01-08}}</ref>

==References==