Transport Layer Security Channel ID: Difference between revisions

Revision as of 09:35, 17 April 2020

Latest revision as of 16:22, 4 January 2022

(One intermediate revision by one other user not shown)

Line 1:

{{multiple issues|

{{primary sources|date=September 2013}}

{{refimprovemore citations needed|date=September 2013}}

}}

'''Transport Layer Security Channel ID''' ('''TLS Channel ID''', previously known as '''Transport Layer Security – Origin Bound Certificates''' '''TLS-OBC''')<ref>[http://tools.ietf.org/html/draft-balfanz-tls-obc-01 TLS-OBC RFC]</ref> is a draft [[Request for Comments|RFC]] proposal<ref>[http://tools.ietf.org/html/draft-balfanz-tls-channelid-01 TLS Channel ID RFC]</ref><ref>{{cite conference |url=https://www.usenix.org/system/files/conference/usenixsecurity12/sec12-final162.pdf |title=Origin-Bound Certificates: A Fresh Approach to Strong Client Authentication for the Web |last1=Dietz |first1=Michael |last2=Czeskis |first2=Alexei |last3=Balfanz |first3=Dirk |last4=Wallach |first4=Dan |date=August 8–10, 2012 |booktitlebook-title=Proceedings of the 21st USENIX Security Symposium}}</ref> [[Transport Layer Security]] (TLS) extension that aims to increase TLS [[computer security|security]] by using [[public key certificate|certificate]]s 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.<ref>[http://security.stackexchange.com/a/12419/396 "Related Domain Cookie Attack"]</ref>{{unreliable source?|date=September 2013}}</ref><ref>[https://stackoverflow.com/q/9636857/328397 additional info is available here]</ref>{{unreliable source?|date=September 2013}}</ref>

==Token Binding==

Line 19:

{{DEFAULTSORT:Transport Layer Security Channel ID}}

[[Category:Transport Layer Security]]

{{security-stub}}