Transport Layer Security Channel ID: Difference between revisions

Revision as of 19:34, 24 September 2013

Revision as of 19:47, 24 September 2013

Line 1:

{{multiple|

{{primary sources|date=September 2013}}

{{ref improve|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-obcchannelid-01 TLS-OBC Channel ID RFC]</ref> that increases [[Transport Layer Security|SSL/TLS]] (TLS) extension that aims to increase TLS [[computer security|security]] by using [[Publicpublic 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"]{{rs|date=September 2013}}</ref><ref>[http://stackoverflow.com/q/9636857/328397 additional info is available here]{{rs|date=September 2013}}</ref>

Line 12 ⟶ 14:

* [http://www.browserauth.net/ TLS-OBC for System Administrators]

{{DEFAULTSORT:Transport Layer Security -Channel Origin Bound CertificatesID}}

[[Category:Transport layer protocols]]