Transport Layer Security Channel ID
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)
|
Transport Layer Security Channel ID (TLS Channel ID, previously known as Transport Layer Security – Origin Bound Certificates TLS-OBC)[1] is a draft RFC proposal[2][3] Transport Layer Security (TLS) extension that aims to increase TLS security by using certificates on both ends of the TLS connection. Notably, the client is permitted to dynamically create a local, self-signed certificate that provides additional security.
It can also protect users from the related domain cookie attack.[4][5]
Token Binding
Token Binding is an evolution of the TLS Channel ID feature,[6] and the IETF draft has Microsoft and Google as authors.[7]
References
- ^ TLS-OBC RFC
- ^ TLS Channel ID RFC
- ^ Dietz, Michael; Czeskis, Alexei; Balfanz, Dirk; Wallach, Dan (August 8–10, 2012). "Origin-Bound Certificates: A Fresh Approach to Strong Client Authentication for the Web" (PDF). Proceedings of the 21st USENIX Security Symposium.
- ^ "Related Domain Cookie Attack"[unreliable source?]
- ^ additional info is available here[unreliable source?]
- ^ "Google Chrome Privacy Whitepaper". Google Inc.
- ^ A. Popov, Ed., M. Nystroem, Microsoft, D. Balfanz, A. Langley, Google (2016-01-08). "The Token Binding Protocol Version 1.0".
{{cite web}}:|author=has generic name (help)CS1 maint: multiple names: authors list (link)
External links
 | This computer security article is a stub. You can help Wikipedia by expanding it. |